Fix Ubuntu Camera Not Detected: Checks for Video and the Webcam Microphone

The short answer

When Ubuntu does not detect a camera, the first question is whether the system sees the device at all. If the webcam does not appear in the USB device list or kernel log, the cause is physical or low-level: cable, port, power, a hardware privacy switch, or a camera disabled in firmware. If the system sees it but an application does not, the cause is usually a driver, a permission, or an app setting. Most USB webcams follow standard device classes that Ubuntu supports without extra drivers. Some recent laptop built-in cameras use newer sensor designs that may need extra support. Without your camera model and Ubuntu version, this guide cannot confirm which group yours is in.

For speech capture, a webcam's microphone is a separate audio device from its camera, even when both are in the same housing. On a USB webcam, video normally uses the USB Video Class (UVC) and the microphone uses the USB Audio Class (UAC). Each is handled by its own kernel driver: uvcvideo for video and snd-usb-audio for sound. Because of this, the camera can be missing while the microphone works, or the reverse. Check both, in the order below.

Step 1: Rule out the physical connection

Start with checks that change nothing on the system.

• Unplug the webcam, wait a few seconds, and plug it directly into a different USB port on the computer, not a hub or dock.
• If the webcam has a detachable cable, try another cable that is known to carry data. Some cables only carry power.
• Check for a physical privacy shutter, slider or kill switch on the camera, plus any camera key on a laptop keyboard. A shutter blocks the image but usually leaves the device detected. A kill switch can remove the device completely.
• On laptops, check whether the built-in camera or microphone has been disabled in the firmware (BIOS/UEFI) setup.

Step 2: Check whether Ubuntu sees the device

Open a terminal and list the connected USB devices. Run the command once with the webcam unplugged and once with it plugged in, then compare the output.

lsusb

Next, look at the kernel messages produced when you plug the device in. Run this command, then connect the webcam and watch for new lines:

sudo dmesg -w

Press Ctrl+C to stop. Here is what each result means:

• No new line in lsusb and nothing in the kernel log: the computer is not seeing the device. Repeat on another port and, if possible, another computer. If it is missing everywhere, a hardware or cable fault is likely, and service or replacement is justified.
• The kernel log shows USB errors, such as messages about failing to enumerate or descriptor read errors: this points to a connection, power or cable problem rather than software. Try a direct port, a powered hub, or a different cable.
• The device appears in lsusb and the kernel log mentions uvcvideo or a USB audio device: the hardware is recognised. Continue to Step 3.
• A laptop's built-in camera does not appear in lsusb: some built-in cameras are not attached over USB. They connect through the processor's imaging hardware, for example Intel IPU-based MIPI cameras. Go to the section on built-in laptop cameras.

Step 3: Confirm the video and audio devices separately

Check for video device nodes and list which device each belongs to. The v4l2-ctl tool comes from the v4l-utils package.

ls /dev/video*
sudo apt install v4l-utils
v4l2-ctl --list-devices

Then check whether the webcam's microphone is registered as a capture (recording) device. The first command lists sound hardware at the ALSA level, which is the kernel sound layer. The second shows what the desktop sound server offers to applications. Recent Ubuntu releases use PipeWire, managed with wpctl. Systems running PulseAudio can use pactl instead.

arecord -l
wpctl status
pactl list short sources

• Video node present and the microphone listed: the system detects both. The problem is in the application or its permissions. Go to Step 4.
• Microphone listed but no video node: the audio interface works, but the video driver did not bind. Check that the uvcvideo module is loaded (Step 5).
• Video node present but no capture device in arecord: the camera may have no microphone, or the audio interface did not initialise. Check the manufacturer's documentation to confirm the model has a microphone, then check the snd_usb_audio module.
• The microphone appears in arecord but not in the sound server: the problem is in the audio session rather than the hardware. Logging out and back in, or restarting the user sound services, is a reasonable next test.

To test speech capture without any conferencing app, record a short clip directly from the webcam microphone and play it back. Replace the card number with the one shown by arecord -l.

arecord -D plughw:1,0 -f S16_LE -r 48000 -d 5 test.wav
aplay test.wav

The results tell you where the fault is. A clear recording means the microphone and driver work, and any remaining problem is in device selection inside your app. A recording that is silent or extremely quiet points to the input level or mute state, or to a hardware fault. Check the level in the system Sound settings or with alsamixer before you conclude it is hardware.

Step 4: Check app permissions and device selection

If the terminal checks show working devices but your browser or conferencing app still reports no camera, the block is usually at the application level.

• Snap packages: Ubuntu often installs apps such as browsers as snaps. Snaps reach the camera and microphone through the camera and audio-record interfaces. Check them with: snap connections <app-name>. Connect a missing one with: sudo snap connect <app-name>:camera (or :audio-record).
• Flatpak apps: review the device permissions in the app's Flatpak settings, or with a permissions manager.
• Browsers: check the site permission for the camera and microphone, and make sure the site has not been blocked.
• In the app's audio and video settings, select the webcam explicitly. Do not rely on a default that may point to a laptop's built-in microphone.
• Only one application can usually hold the camera at a time. Close other video apps and retry. To see which process holds the camera, run: sudo fuser /dev/video0

Step 5: Check the kernel drivers

Confirm that the standard modules are loaded. If one is missing, you can try loading it manually. This change is reversible and lasts only until you reboot.

lsmod | grep -E 'uvcvideo|snd_usb_audio'
sudo modprobe uvcvideo
sudo modprobe snd_usb_audio

If the camera stopped working after a system update, try booting the previous kernel. Hold Shift or press Esc during startup to open the GRUB menu, then choose the older kernel under Advanced options. If the camera works on the older kernel, a kernel change is likely involved. Report it through Ubuntu's bug tracker with your device's ID from lsusb. This is a diagnostic result, not proof of the specific cause.

Built-in laptop cameras that never appear

Some recent laptops use MIPI camera sensors connected through Intel's IPU6 or similar imaging hardware instead of USB. These cameras do not show up in lsusb. Support on Ubuntu has depended on the specific laptop, sensor and release, sometimes through additional driver packages. Ubuntu and some laptop vendors have published support for certain models. The supplied material does not include a compatibility list, so this guide cannot say whether your laptop is covered. Check the vendor's Linux support notes or Ubuntu's hardware certification information for your exact model.

For speech capture on these laptops, the built-in microphone array is usually a separate audio device on the laptop's sound hardware, not part of the camera. A missing camera does not mean the microphone is missing, and the reverse also holds. Check the microphone with the arecord and Sound settings steps above.

When service or replacement is justified

• The webcam is missing from lsusb on every port and on a second computer: a hardware or cable fault is the most likely explanation.
• The kernel log shows repeated USB connection errors on several ports and cables: this is also likely to be a hardware fault.
• The webcam works on another operating system but no Ubuntu kernel detects it: this points to a compatibility gap. A webcam advertised as UVC-compliant, from a model with documented Linux support, is the safer replacement choice.
• The microphone records only silence at maximum input level while the system detects it correctly: the microphone capsule or its internal connection may have failed. A separate USB microphone or headset is often a more reliable choice for speech than replacing the webcam.

What this guide cannot confirm

The supplied evidence includes no details about specific webcam models, Ubuntu releases or driver versions. It also includes no test recordings or measured audio quality. The steps above are standard diagnostic procedures. They identify which layer is failing, but they do not establish the root cause for a particular device. If you need model-specific confirmation, gather the device ID from lsusb, the relevant kernel log lines and your Ubuntu version, and compare them against the manufacturer's or Ubuntu's own documentation.