1814373 - internal dell webcam reported in use

Status: RESOLVED DUPLICATE of bug 1802117

(Core :: Audio/Video, defect)

Description

[John Zooi]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/109.0

Steps to reproduce:

after the upgrade of firefox to 109.0.1 from: https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu on Kubuntu 22.04 (up2date).

Opening any video meeting site (nextcloud talk, teams, etc etc) firefox reports that the device is busy, and is unable to use the webcam.

Actual results:

Open the site, start meeting, select the Intel Mipi webcam resolves in a notification that the webcam is already in use.
fuser /dev/video0 reports that it is firefox using the webcam.

After trying to use the webcam, other applications aren't able to use the webcam (cheese, chroimium etc).
after closing firefox, other applications re able to open and use the webcam.

Tested the following: firefox closed, fuser doesn't show any apllication using the webcam.
start firfox, fuser still doesn't show the webcam being used.
start meeting, fuser shows the webcam being used by firefox.

The weird thing here, I also have al logitech C920, this one works in firefox.

Expected results:

The internal webcam should work, just like it did until firefox updated yesterday.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[John Zooi]

Update:
still an issue in 110.0 (64-bit)
starting firefox in clean new profile with no plugins, results in the same thing. firefox is the only application having issues accessing the integrated camara. My colleague, which has a previous generation xps13, has the same issue on his camara, He uses the snap image.

Comment 3

[Martin Stránský [:stransky] (ni? me)]

Can you try plain Mozilla binaries?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_Mozilla_binaries
Thanks.

Comment 4

[John Zooi]

using the latest from the ppa, and the latest Mozilla binaries of Firefox 110.1 result the same behavior. The messege remains the device is in use.

Can a gather anymore useful info?

Comment 5

[az [:az]]

I gave this a try with the Firefox PPA on Ubuntu 22.10 and was unable to repro. Would you be able to install mozregression to help narrow down the changes that caused this bug? If you're comfortable with pip, you can run pip install mozregression from within a virtual environment to install, or pip install --user mozregression otherwise. Then, you can run mozregression --good 2022-11-14 --bad 2023-01-16. Firefox will launch with a fresh profile and the terminal will prompt asking whether the build is good or bad. Test the webcam and answer the prompt. The process will repeat several times with different builds and when it completes you'll have output like the following:

Was this integration build good, bad, or broken? (type 'good', 'bad', 'skip', 'retry' or 'exit' and press Enter): good
 1:57.42 INFO: Narrowed integration regression window from [3ccb0b86, 370b8894] (3 builds) to [4d46db3f, 370b8894] (2 builds) (~1 steps left)
 1:57.42 INFO: No more integration revisions, bisection finished.
 1:57.42 INFO: Last good revision: 4d46db3ff28b5b4f80c3587e77f1e162e552b5e0
 1:57.42 INFO: First bad revision: 370b88940241e124a82dee16c6fce90ee25af36b
 1:57.42 INFO: Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=4d46db3ff28b5b4f80c3587e77f1e162e552b5e0&tochange=370b88940241e124a82dee16c6fce90ee25af36b

If you could paste that output here, it'd help diagnose further. Thank you!

Comment 6

[az [:az]]

If possible, logs for the webcam working and failing cases would be useful too. This short video shows how to configure, collect, and share logs, though you will want to use the "custom" logging preset with the following log modules:

CamerasChild:5,CamerasParent:5,MediaManager:5,VideoEngine:5

Let me know if you run into any issues. Thanks!

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

Setting Regressed by field after analyzing regression range found by mozregression in comment #5.

Comment 8

[az [:az]]

Bot incorrectly changed this bug based on sample output from the regression tool, so I'm reverting those changes.

Comment 9

[John Zooi]

Attachment: webcam_broken.txt-main.3631.moz_log

Log file as requested, of using the webcam which isn't working.

Comment 10

[John Zooi]

Attachment: webcam_working.txt-main.3631.moz_log

logfile of switching to the working webcam

Comment 11

[John Zooi]

Sorry for the late response, been really busy.

I have 2 log files,
webcam broken is trying to use the ipmi internal webcam, which isn't working.
webcam working, is the log, switching from the ipmi to the working logitech c920.

Comment 12

[Jim Mathies [:jimm]]

Maybe andreas has some ideas.

Comment 13

[Andreas Pehrson [:pehrsons]]

You need to set the log modules mentioned in comment 6 as "Custom" for the logs to be useful for debugging video capture.

In addition to them could you also, prior to starting the logging, do:

• Go to about:webrtc and click Start Debug Mode
• Add another log module to the custom list, so in total you get CamerasChild:5,CamerasParent:5,MediaManager:5,VideoEngine:5,webrtc_trace:5

Comment 14

[Andreas Pehrson [:pehrsons]]

The mozregression results would possibly be even more useful, fwiw.

Comment 15

[Andreas Pehrson [:pehrsons]]

Hang on, this sounds like bug 1802117, which should be fixed on beta (114). Please re-open or re-file if that is incorrect.

That a camera that failed to start is not properly stopped is a known issue that we'll get to eventually.

Comment 16

[John Zooi]

Ah nice!

great that there will be a fix.