[pulseaudio-discuss] problem with webrtc and pulseaudio

Tanu Kaskinen tanuk at iki.fi
Thu Feb 16 10:42:21 UTC 2017

On Wed, 2017-02-15 at 16:44 -0300, Fatima Castiglione Maldonado 发
> > The strange thing is that earlier you got some sound from chrome, andes
> > if I understood correctly, you had pavucontrol open. If you have
> > pavucontrol open, and you can see activity in the mic volume meter, it
> > means that pulseaudio is using the microphone, and usually other
> > applications can't use the microphone at the same time if they try to
> > use the hardware directly, bypassing pulseaudio. Maybe in that instance
> > chrome managed to create a recording stream in pulseaudio?
> I did it again to be sure, and yes, pavucontrol runs and shows input, and
> at the same time bigbluebutton runs on chrome and echoes my voice with a
> cracking sound

When you say "shows input", do you mean that the microphone shows
activity on the "Input Devices" tab, or that there's a stream for
chrome visible on the "Recording" tab?

The earlier pulseaudio log didn't show any recording streams from
chrome. If you manage to get chrome to create a recording stream
(you'll see it in the "Recording" tab of pavucontrol), a new log might
show something, although I'm not particularly optimistic about that.

To narrow down the problem further, you could try recording from the
microphone at the same time when chrome is supposed to be recording
from it. You can use this command:

parecord --device=alsa_input.pci-0000_00_1b.0.analog-stereo test.wav

When you play back that test.wav file, does it contain better
microphone audio than what chrome produces?

> And yes, there is an error nmessage in my terminal (please look at latest
> line)
> /usr/bin/google-chrome-stable %U
> [2613:2613:0215/125529.812664:ERROR:gl_surface_glx.cc(406)] glxQueryVersion
> failed
> [2613:2613:0215/125529.812964:ERROR:gl_initializer_x11.cc(130)]
> GLSurfaceGLX::InitializeOneOff failed.
> [2613:2613:0215/125529.829241:ERROR:gpu_child_thread.cc(327)] Exiting GPU
> process due to errors during initialization
> [2527:2561:0215/125530.039051:ERROR:browser_gpu_channel_host_factory.cc(113)]
> Failed to launch GPU process.
> [2527:2561:0215/125530.049017:ERROR:browser_gpu_channel_host_factory.cc(113)]
> Failed to launch GPU process.
> [2527:2561:0215/125530.057225:ERROR:browser_gpu_channel_host_factory.cc(113)]
> Failed to launch GPU process.
> [2527:2561:0215/125530.059328:ERROR:browser_gpu_channel_host_factory.cc(113)]
> Failed to launch GPU process.
> [2527:2561:0215/125530.061832:ERROR:browser_gpu_channel_host_factory.cc(113)]
> Failed to launch GPU process.
> [2527:2561:0215/125530.064292:ERROR:browser_gpu_channel_host_factory.cc(113)]
> Failed to launch GPU process.
> [WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
> [WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
> [1:23:0215/125626.008144:ERROR:audio_send_stream.cc(90)] Failed to set up
> send codec state.

That error doesn't unfortunately tell me much. This looks more like
something that Chrome developers should look at.



More information about the pulseaudio-discuss mailing list