this post was submitted on 17 Feb 2025
9 points (84.6% liked)

No Stupid Questions

2504 readers
35 users here now

There is no such thing as a Stupid Question!

Don't be embarrassed of your curiosity; everyone has questions that they may feel uncomfortable asking certain people, so this place gives you a nice area not to be judged about asking it. Everyone here is willing to help.


Reminder that the rules for lemmy.ca still apply!


Thanks for reading all of this, even if you didn't read all of this, and your eye started somewhere else, have a watermelon slice ๐Ÿ‰.


founded 2 years ago
MODERATORS
 

edit: I am a fool! Just needed to disable chameleon. thanks!

It was working fine a few weeks ago, then randomly stopped detecting mic/camera. Did Google get tired of me not using Chrome? Lol

I have an old HP envy 360 (internal camera and mic) Fedora 41 with KDE Plasma Firefox browser

Zoom (app), Updox (browser), and a few others still work fine. I set it to always allow camera & mic but no dice.

Old forum posts sadly did not fix it either :(

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 2 points 1 week ago* (last edited 1 week ago) (1 children)

Oh, sorry, gotcha.

Well, yeah, that I have a hard time finding a plausible explanation for, unless Firefox has per-device, per-site permissions. I assume that it only has per-site permissions.

I'd maybe run something like:

$ sudo lsof -n|grep /dev/video

...prior to going to the page that does this, to see whether any other software has the device open. I don't know if that could produce that behavior, but that's the only thing that I could think of at the OS level. Otherwise, gotta be something at the Firefox level.

Maybe you have multiple tabs or windows open that are using the camera, and Firefox constrains only one to concurrently use the thing?

EDIT: Maybe check, using cheese or some similar app, or another website right then that you can use the camera at that point? I mean, I can maybe imagine the camera or its driver or something having an issue, and the failure mode being for the device not to be visible at the Firefox menu level. I mean, I've seen, say, Bluetooth or controllers that get into a wonky state after unsuspending and for the result to be that they aren't visible to applications. Reboot clears it up, but maybe you could have just been unlucky that the time you tried using Google Meet was the time that you had the issue?

[โ€“] [email protected] 1 points 1 week ago

Hi, thank you for spending so much time on this. I feel foolish because I just had to disable chameleon. But I really appreciate it as I am still learning Linux and I think it makes me forget the simple stuff.