Ubuntu 24.04 ships with GNOME's new camera app and it doesn't work. It simply fails to recognize the in-built or external webcams.
When you open the Camera app, it shows "No Camera Found. Connect a camera device" message.
This may make you doubt your machine's hardware but it likely to be a software issue as the Camera app does not work by default in Ubuntu 24.04.
Several workarounds have been suggested for this problem on various Ubuntu forums. However, the one that worked for me was shared by an It's FOSS reader, Jack.
Here it is.
Fixing the issue
The trick here is to add yourself to the video
group. You can use the usermod command for this purpose. Fortunately or unfortunately, this is a command line fix.
-a
part is of utmost important.Open a terminal in Ubuntu (use Ctrl+Alt+T shortcut) and run the following command:
sudo usermod -aG video $USER
If this is your first time with sudo, you should know that it asks to enter password. You have to enter your account's password through which you log into the system. While typing the password, nothing is reflected on the screen. That's normal in the UNIX/Linux world. Just blindly type the password and press enter.
There is no success message or output for the command.
π‘ The usermod command modifies a user account. With G
you are telling it to modify the groups the user belongs. The -a
option is crucial because you are asking it to append a new group to existing groups of a user. If you don't use -a
, then user will only belong to the group you specify (video here) and that will be catastrophic as you cannot use sudo and function as before.
You may have to log out or restart the system before the changes take effect.
When you start the Camera app again, it should work now.
Conclusion
I still prefer the good old Cheese camera app.
If you want, you can install it using this command:
sudo apt install cheese
It is also available from the app store but the Snap version gets priority and that also doesn't work very well.
Each Ubuntu release has bugs, 24.04 is just buggier. I don't understand how this prevalent bug made it to a long-term support release and why it has not been fixed even after the first point release of 24.04.1.
I know we are not going to get answers but at least these troubleshootings help us explore an otherwise uncharted territory.