Microphone stops working during Hangouts calls
Reported by
theo.bri...@gmail.com,
Feb 9 2018
|
||||||||||||
Issue descriptionChrome Version : 64.0.3282.119 (Developer Build) (64-bit) OS version : Linux 4.14.15-1-ARCH (arch linux) Network (such as Cable/DSL/Dial up etc): Wifi Video issue, Audio issue, both, neither? Microphone issue Flash or HTML5? HTML5 If the browser or renderer crashed (“Aw, Snap”), please add any crash IDs from chrome://crashes (possibly after enabling crash reporting per http://support.google.com/chrome/bin/answer.py?hl=en&answer=96817) What steps will reproduce the problem? I did not managed to reproduce this, it keeps happening from time to time. What is the expected result? The microphone should keep on working during the whole hangouts call. What is the actual result? The microphone stop working during hangouts call Any additional information (anything else which may help us debug the issue)? I am running Arch Linux on a Dell XPS 13 (9360) When my microphone stops the only solution I have so far is to restart the hangouts session by closing the tab and re-opening it. I checked if my microphone was still working after it stopped in a hangouts session, by using: `arecord|aplay` and it was working correctly. My sound card is managed through snd_hda_intel module, from which I have disabled the power saving option using: ``` $ cat /etc/modprobe.d/modprobe.conf options snd_hda_intel power_save=0 power_save_controller=N ``` but this did not help. You can find attached the WebRTC log of a hangouts session where my microphone stopped working.
,
Feb 12 2018
Unable to reproduce the issue on linux Ubuntu 14.04 using chrome reported version-64.0.3282.119 & latest stable-64.0.3282.140 as per the above steps. Able to join hangouts call & speak & listen without any microphone issue during the call. Could you please check the issue on latest chrome stable version with clean profile .Seems issue specific to 'Arch Linux on a Dell' system.Please confirm? Thanks..!
,
Feb 12 2018
Just updated my chromium to 64.0.3282.140, but the issue is still present. I am not sure if this is specific to 'Arch Linux on a Dell' did not found anyone having the same issue.
,
Feb 12 2018
Thank you for providing more feedback. Adding requester "jmukthavaram@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 13 2018
Unable to reproduce the issue on ubuntu 14.04 using chromium reported version #64.0.3282.119 (Developer Build) (64-bit). Following are the steps followed to reproduce the issue. ------------ 1. Joined hangout using hangouts.google.com 2. Observed that microphone worked without any issues. Removing Needs-Bisect label as it is not reproducible from TE-end and requesting someone from Internals>Media team to please have a look into the issue. Thanks...!!
,
Mar 6 2018
The issue is not reproducible from TE-end and Arch Linux is not available with TE. Hence, adding label TE-NeedsTriageHelp for further investigation from dev team. Thanks...!!
,
Mar 6 2018
I am not sure this issue is coming from chromium, but hangout since hangout only works on chromium. I had no way to test that on different browser. How would you guys proceed with debugging it?
,
Mar 23 2018
,
Apr 2 2018
,
Apr 5 2018
Do you get a "the microphone stop working" indication in Hangouts or the remote end just won't hear you any more? Next time when it happens could you please collect the following info in addition to WebRTC log During the call: * Media-internals (chrome://media-internals) Browse to chrome://media-internals and select the players tab Select each button and select copy to clipboard, then paste into a text file/doc. Repeat this for each button seen. This is quite cumbersome, we know, a bug has been filed for improving this. Select the audio tab and repeat step 3. Attach/link the doc to the bug. * Webrtc-internals (chrome://webrtc-internals) Browse to chrome://webrtc-internals Expand create dump at the top of the page Select Download the PeerConnection updates and stats data Select the getUserMedia request tab Select all the requests and copy them into a text file/doc Attach/link the doc to the bug. * Diagnostic debug recording: open a new tab go to chrome://webrtc-internals click on “Create Dump” to expand click on “Enable diagnostic audio recordings.” choose an appropriate location for the files to be stored and a base filename. make sure the “Enable diagnostic audio recordings.”-box is ticked. You are now recording! Please attach/link the recording to the bug (~10 seconds of recorded sound would be enough). Thanks!
,
Apr 5 2018
For Hangouts issues, it's preferable to file a Hangouts feedback report since the issue can be anywhere. That report will collect a lot of information useful for debugging, and will end up with the right team. |
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by manoranj...@chromium.org
, Feb 9 2018