Fix a Laptop Camera Showing a Black Screen on Ubuntu

The short answer

A black camera image on Ubuntu usually comes from one of a small set of causes. The camera may be blocked by a privacy shutter, a function key or a firmware setting. The app may have picked the wrong video device, such as an infrared face-login sensor or a metadata node. Another program may already be using the camera. A sandboxed app may lack permission. Or the laptop may use a camera type that your Ubuntu release does not support out of the box.

Whether you need to install a driver depends on how the camera connects. Most webcams follow the USB Video Class (UVC) standard. That includes many built-in laptop cameras, which are wired to an internal USB connection. UVC cameras use the uvcvideo driver that ships with the Linux kernel, so there is normally nothing to install. Driver work becomes relevant mainly for MIPI cameras, which connect through an image processing unit such as Intel's IPU6 on many recent Intel laptops. Support for those depends on the specific laptop model and Ubuntu release. No model-specific evidence was supplied for this guide, so check your manufacturer's Linux support information for your exact model.

Why the microphone needs a separate check

Video and audio take separate paths, even when they live in the same housing.

• External USB webcam: the camera and microphone usually appear to the system as two separate functions on one USB device, a video function and a USB Audio Class function. The microphone can keep working while the video is black. If the whole device fails to connect over USB, both are lost.
• Built-in laptop microphone: this is commonly wired to the laptop's audio hardware rather than the camera module. A camera fault therefore does not necessarily affect it. This is a general pattern, not something verified for any particular model.

In practice, if your goal is to be heard on a call, the microphone may already work. Test it on its own (step 9 below) before assuming the camera problem has taken your audio with it.

Isolate the cause step by step

Every check below is reversible. Work through them in order. Treat each suspected cause as a guess until the result of a check supports it.

1. Rule out physical and firmware blocks

Look for a sliding shutter over the lens. Check whether a function key toggles the camera; some laptops show an indicator light or an on-screen message when you press it. Check the firmware setup (BIOS/UEFI) for a camera enable option.

• If the shutter was closed or the camera was disabled, re-enable it and test again.
• If a shutter blocks the lens, the device usually still appears to the system and streams frames, but the frames are dark. Seeing the device listed does not rule out a shutter.

2. Close other apps and try a second camera app

Quit browsers, conferencing clients and any other app that might hold the camera. Then test with a simple camera viewer such as GNOME's Snapshot or Cheese, or a tool like guvcview.

• If the image works in one app but not another, the camera itself is fine. Look at that app's device selection or permissions (steps 4 and 6).
• If every app shows black or reports no camera, continue to step 3.

3. Confirm Ubuntu detects the camera

Open a terminal and list the USB devices and video devices. The v4l2-ctl command comes from the v4l-utils package, so install that first if it is missing.

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

• Camera listed in lsusb with /dev/video nodes present: the driver has loaded. The likely causes are device selection, permissions or a blocked lens.
• Camera listed in lsusb but no /dev/video nodes: the driver may have failed to bind. Check kernel messages in step 5.
• Nothing camera-like in lsusb: the camera may be disabled in firmware, may be a MIPI camera that does not appear as USB (step 8), or may have a hardware fault.

4. Make sure the app uses the right device

A single camera often creates more than one /dev/video node. Usually one node carries the image and another carries only metadata. Laptops with infrared face login also have a separate IR camera. The IR camera can show a dark, grainy or black picture in an ordinary camera app.

Use v4l2-ctl to see which formats each node offers. Replace video0 with each node in turn. A node that lists common formats such as YUYV or MJPG at normal resolutions is usually the colour camera. Then select that device in your app's camera settings.

v4l2-ctl -d /dev/video0 --list-formats-ext

5. Read the kernel messages

sudo dmesg | grep -iE 'uvc|ipu|camera|video'

• Messages showing the uvcvideo driver found the device, with no errors: the driver side looks healthy.
• Repeated errors, timeouts, or the device disconnecting and reconnecting: this suggests a firmware, power or connection problem. For an external webcam, try another port and cable. For a built-in camera, it can point to hardware.
• Messages mentioning IPU or a MIPI sensor: continue to step 8.

6. Check app permissions

Apps installed as Snap or Flatpak packages run in a sandbox and need explicit camera access.

• Snap apps: list the app's connections and look at the camera interface. Replace appname with the app's snap name.
• Flatpak apps: check the app's device permissions with a tool such as Flatseal.
• GNOME Settings: recent versions include a camera privacy section. If your release has one, make sure the app is allowed there.

snap connections appname
sudo snap connect appname:camera

7. Reload the UVC driver

Close every app that uses the camera, then unload and reload the driver. A reboot does the same job.

sudo modprobe -r uvcvideo
sudo modprobe uvcvideo

If the image returns after reloading but fails again later, note what triggers it, such as resuming from suspend. That points to a driver or firmware issue worth reporting, rather than a setting you can fix yourself.

8. Check whether the camera is MIPI and needs extra support

lspci | grep -iE 'ipu|multimedia|imaging'

If this shows an image processing unit and the camera never appeared as a USB device in step 3, the laptop probably uses a MIPI camera. Support for these depends on kernel drivers, a camera software layer and the specific sensor. It has varied between Ubuntu releases and laptop models. Some machines sold with Ubuntu preinstalled have shipped with the needed components.

• Check whether your manufacturer lists your exact model as supported on your Ubuntu release.
• Test with a live USB of the newest Ubuntu release. If the camera works there, upgrading or using the components that release provides is a reasonable next step.
• Prefer the manufacturer's or Ubuntu's own packages over third-party driver builds. If you do build drivers yourself with DKMS while Secure Boot is on, the modules may need signing before they will load.

9. Verify the microphone independently

Whatever the camera result, check that the audio input exists and actually records sound. First list the capture devices and audio sources. Then make a short test recording and play it back. The wpctl command applies to systems running PipeWire, which recent Ubuntu releases use by default; pactl also works on those systems.

arecord -l
wpctl status
pactl list short sources
arecord -d 5 -f cd test.wav
aplay test.wav

• Webcam microphone listed and the recording contains your voice: audio works. In your conferencing app, choose it as the input device, or choose another microphone if you prefer.
• Microphone listed but the recording is silent or very quiet: check that the input is not muted, and raise the input level in Settings under Sound. Then record again.
• No webcam microphone listed even though lsusb shows the webcam: the audio function may have failed to load. Check dmesg for USB audio errors.
• Neither the webcam's video nor its microphone appears: the whole device is failing to connect. Suspect the port, cable, power or the device itself.

When repair or replacement is justified

Booting a live USB of the latest Ubuntu release is the clearest test for separating a configuration problem from a hardware fault.

• Built-in camera: if it is enabled in firmware and still does not appear on the live system, and the manufacturer's diagnostics also fail to detect it, a hardware or internal cable fault is likely. Consider warranty service.
• External webcam: if it fails on several computers and ports, replacement is reasonable.
• MIPI camera with no support for your model: an external UVC webcam is a practical workaround, since it uses the standard kernel driver. Judge its microphone separately by recording your own speech, because no voice-quality evidence was supplied here for any model.

Gaps in the available evidence

This guide gives general diagnostic steps. It does not confirm camera or microphone support for any particular laptop, sensor or Ubuntu release, and it includes no measurements of webcam microphone quality. For model-specific driver status, rely on your manufacturer's Linux documentation and on testing with a current live USB.