1030614 - Camera access with Logitech Quick Cam Communicate STX broken since 31.0

Status: RESOLVED WORKSFORME

(Core :: WebRTC: Audio/Video, defect)

Description

[Sebastian Kummer]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release)
Build ID: 20140623175014

Steps to reproduce:

- Open Firefox 31.0 on a Windows PC
- Connect a "Logitech Quick Cam Communicate STX" Webcam to your PC
- Open the WebRTC Reference App at https://apprtc.appspot.com/
- Allow camera access


Actual results:

Error Message: "Failed to get access to local media. Error name was undefined."

Console-Log:
"This appears to be Firefox" adapter.js.pagespeed.jm.AkolCSL177.js:5
"0.617: Initializing; room=66832172." adapter.js.pagespeed.jm.AkolCSL177.js:2
"0.618: Opening channel." adapter.js.pagespeed.jm.AkolCSL177.js:2
"0.624: Requested access to local media with mediaConstraints:
  '{"audio":true,"video":true}'" adapter.js.pagespeed.jm.AkolCSL177.js:2
"0.948: Channel opened." adapter.js.pagespeed.jm.AkolCSL177.js:2
"3.469: Failed to get access to local media. Error name was undefined. Continuing without sending a stream."


Expected results:

The camera should have been accessed and a stream should be sent.

Comment 1

[Sebastian Kummer]

The same camera hardware worked with earlier Firefox versions and still does with Google Chrome Browser.

Comment 2

[Sebastian Kummer]

Other people are experiencing the same issue on different hardware; already since FF 30, see https://groups.google.com/forum/#!topic/discuss-webrtc/7x3u-4MsGzw

Comment 3

[sergio.garcia.murillo]

Yes, since Firefox 30 the Lenovo laptops fails to detect the camera in getUserMedia. 

We tested one laptop with FF 29 and it was working, upgraded to 30 and it stopped working.

Comment 4

[:Gijs (he/him)]

(In reply to sergio.garcia.murillo from comment #3)
> Yes, since Firefox 30 the Lenovo laptops fails to detect the camera in
> getUserMedia. 
> 
> We tested one laptop with FF 29 and it was working, upgraded to 30 and it
> stopped working.

This sounds like a separate issue as it concerns different hardware and broke at a different point in time. Please file a separate bug if you haven't already.

(In reply to Sebastian Kummer from comment #1)
> The same camera hardware worked with earlier Firefox versions and still does
> with Google Chrome Browser.

Would you be willing to try to obtain a regression window using mozregression ? ( https://github.com/mozilla/mozregression )

Comment 5

[Randell Jesup [:jesup] (needinfo me)]

Also, if you download a debug build from ftp.mozilla.org (such as from http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/) and set NSPR_LOG_MODULES=getusermedia:5,mediamanager:5 and NSPR_LOG_FILE=some_temp_location and run firefox, it should get us some useful data.

We did add support for motion-jpeg capture in the last 6(?) months; it's possible that impacted this.  (most cameras require MJPEG above VGA resolution, some at all resolutions)

Comment 6

[Sebastian Kummer]

Attachment: log-all-level-5

Setting NSPR_LOG_MODULES=getusermedia:5,mediamanager:5 created an empty file but did not log anything - so I added all:5

You can see the displayed error in the log:
2014-06-27 12:23:46.565000 UTC - 2888[2d129b0]: Latency: MediaStream Create,205207776,0,205207472
2014-06-27 12:23:46.577000 UTC - 0[2d0f140]: (textrun) fontgroup: [Verdana,Arial,Helvetica,sans-serif] default: serif lang: de-de script: 25 len 99 weight: 400 width: 0 style: normal size:  16,00 1-byte TEXTRUN [Failed to get access to local media. Error name was undefined. Continuing without sending a stream.] ENDTEXTRUN

Comment 7

[Randell Jesup [:jesup] (needinfo me)]

(In reply to Sebastian Kummer from comment #6)
> Created attachment 8447131 [details]
> log-all-level-5
> 
> Setting NSPR_LOG_MODULES=getusermedia:5,mediamanager:5 created an empty file
> but did not log anything - so I added all:5

As with many debugs in the code, you need a debug build to see these.  You can download debug builds from the link I gave above.

The data in all:5 isn't very helpful here; all the debugs in the modules in question aren't compiled in for opt builds.

Comment 8

[sergio.garcia.murillo]

(In reply to :Gijs Kruitbosch from comment #4)
> (In reply to sergio.garcia.murillo from comment #3)
> > Yes, since Firefox 30 the Lenovo laptops fails to detect the camera in
> > getUserMedia. 
> > 
> > We tested one laptop with FF 29 and it was working, upgraded to 30 and it
> > stopped working.
> 
> This sounds like a separate issue as it concerns different hardware and
> broke at a different point in time. Please file a separate bug if you
> haven't already.

I have done it (#1032231) and also attached the log files from the debug version as requested.

> 
> (In reply to Sebastian Kummer from comment #1)
> > The same camera hardware worked with earlier Firefox versions and still does
> > with Google Chrome Browser.
> 
> Would you be willing to try to obtain a regression window using
> mozregression ? ( https://github.com/mozilla/mozregression )

Sure, how?

Comment 9

[Sebastian Kummer]

Attachment: Debug_1_logitech_quickcam_audio_and_video_ERROR

Comment 10

[Sebastian Kummer]

Attachment: Debug_2_logitech_quickcam_video_only_OK

Comment 11

[Sebastian Kummer]

Attachment: Debug_3_c525_audio_and_video_OK

I attached three debug logs. The problem seems to be audio - not video.

Log #1: Selecting the QuickCam as Audio and Video Device -> Media Error
Log #2: Selecting the QuickCam as Video Device and "No Audio" -> OK
Log #3: Selecting another Webcam (C525) as Audio and Video Device -> OK

Comment 12

[Randell Jesup [:jesup] (needinfo me)]

2014-06-30 19:33:08.017000 UTC - 9048[14b5d548]: Starting audio failed , rv=-2147467259

Ok, as you say audio failed.

To go further, we need internal logs.  Open the browser (recently nightly - debug or not), open a tab to about:webrtc, click on "Start debug mode".  Then go to http://mozilla.github.com/webrtc-landing/gum_test.html and try capturing audio.  After say 5 or 10 seconds, you can close the tab/browser.  The log file should be in %TEMP% on windows; or /tmp on mac or linux.

Comment 13

[Sebastian Kummer]

If I go to about:webrtc the only button displayed is "Show/refresh logging". Clicking it has no visible effect. 

Result from http://mozilla.github.io/webrtc-landing/gum_test.html
- Video: Success
- Audio: Success
- Audio & Video: Starting audio failed

There is no new file created in %TEMP%

Comment 14

[Randell Jesup [:jesup] (needinfo me)]

The logging button is only available on Nightly and Aurora ("Open the browser (recently nightly - debug or not)")

Comment 15

[Sebastian Kummer]

I had to uninstall Nightly-Debug and install the regular Nightly to get the "Start Debug Mode" button. However, in Nightly version 33.0a1 (2014-07-02) the problem does no more occur.