Logitech C930 audio captures no sound on Linux Mint

Introduction

When you connect a Logitech C930 webcam to a Linux Mint machine, you expect a single plug‑and‑play experience: a high‑definition video feed and a built‑in microphone that feeds audio into your video calls or recording software. While most users find that the video stream works flawlessly, many report a silent audio channel. This article walks you through a systematic process to diagnose and fix the issue. The guidance applies to Linux Mint 20 (which uses PulseAudio) and Linux Mint 21 (which uses Pipewire by default) but is also relevant to older or newer Mint releases.

The troubleshooting strategy is threefold:

1. Verify that the hardware is recognised by the kernel and exposed as an audio device.
2. Confirm that the system’s sound stack (PulseAudio or Pipewire) is loading the correct modules and presenting the webcam microphone as a source.
3. Test the audio path with low‑level tools such as arecord and ffmpeg and then configure your favourite application (OBS, Zoom, Discord, etc.) to use that source.

Throughout the article we use command‑line tools because they provide the most insight into what the system is actually doing. If you prefer a graphical approach, the same concepts apply – just use the corresponding GUI utilities.

1. Check the Physical Connection

Before diving into software, make sure the webcam is physically connected correctly.

• Plug the webcam into an external USB port rather than a USB hub or a port that is known to supply a weak signal.
• If you are using a docking station, try connecting the camera directly to the laptop or desktop.
• Swap the USB cable if you suspect a faulty cable.

These simple steps eliminate the most common hardware faults.

2. Inspect the Kernel’s View of the Device

The first software check is to see whether the kernel has detected the webcam and created the necessary device nodes.

2.1 Confirm USB Enumeration

Run:

lsusb

You should see a line similar to:

Bus 002 Device 003: ID 046d:08d5 Logitech, Inc. C930

If the device is not listed, the kernel has not seen it. Try a different USB port or cable.

2.2 Examine the Audio Subsystem

Use the arecord tool from the alsa-utils package to list all recording devices:

arecord -l

Typical output for a functioning Logitech C930 audio device looks like:

**** List of CAPTURE Hardware Devices ****
card 1: LogitechC930 [Logitech C930], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

If you see a card with a USB Audio description, the kernel driver snd_usb_audio has bound to the device and exposed an ALSA capture device.

If the card is missing, load the module manually:

sudo modprobe snd_usb_audio

Then run arecord -l again. If the device still does not appear, check the kernel logs:

dmesg | grep -i usb

Look for lines indicating an error loading snd_usb_audio or for the device being marked as unsupported.

2.3 Verify the ALSA Card List

cat /proc/asound/cards provides a concise view:

 0 [Loopback  ]: Loopback - Loopback PCM
 1 [LogitechC] 0: Logitech C930 (hw:1,0)

The card number (1 in the example) will be used later to reference the device in PulseAudio or Pipewire.

3. Adjust Group Membership

Linux audio hardware is typically owned by the audio group and USB video devices belong to the video group. If you are not a member of either group, the system may refuse to open the device.

sudo usermod -aG audio $USER
sudo usermod -aG video $USER

Log out and log back in for the group changes to take effect. After re‑login, re‑run arecord -l to confirm that the device is accessible.

4. PulseAudio (Linux Mint 20 and earlier)

4.1 Ensure the Correct Module is Loaded

PulseAudio needs to load the module-alsa-sink and module-alsa-source modules. Open the default PulseAudio configuration file:

sudo nano /etc/pulse/default.pa

Confirm that the following lines are present (they are usually in the default configuration):

load-module module-alsa-sink
load-module module-alsa-source

If they are commented out or missing, add or uncomment them. Save the file and restart PulseAudio:

pulseaudio -k
pulseaudio --start

4.2 Verify the Source in PulseAudio

Run:

pactl list sources short

You should see an entry similar to:

1   LogitechC930    module-alsa-source   1   1   yes

If the source is not listed, PulseAudio is not exposing the device. Try reloading the module manually:

pactl load-module module-alsa-source device=hw:1,0

Replace hw:1,0 with the card and device numbers from the ALSA output. After loading, re‑run the pactl list sources command to verify.

4.3 Test with arecord

Use the ALSA tool directly to confirm audio capture:

arecord -D hw:1,0 -f cd -t wav -d 5 test.wav

This command records 5 seconds of audio from the webcam and writes it to test.wav. Play the file:

aplay test.wav

If you hear sound, the hardware and kernel are fine; the issue is with PulseAudio or the application you are using. If the recording fails, return to section 2.

4.4 Use pavucontrol for GUI Control

Install the PulseAudio volume control if you don’t already have it:

sudo apt install pavucontrol

Open it:

pavucontrol

Navigate to the Input Devices tab and locate the webcam microphone. Ensure that it is not muted and that the input level is not at zero. Also check the Recording tab when an application is capturing audio to confirm that the source is selected correctly.

4.5 Common PulseAudio Quirks

• Automatic Mute: Some kernels automatically mute the webcam microphone when a video stream is active. To disable this, add the following line to /etc/pulse/daemon.conf:

  avoid-resampling = yes
  

  Then restart PulseAudio.

• User‑Space Permissions: If the microphone still does not appear, check /etc/pulse/ for user‑specific configuration. Remove any client.conf or daemon.conf that might override the defaults.

5. Pipewire (Linux Mint 21 and later)

Linux Mint 21 switches to Pipewire by default, which replaces PulseAudio for both audio and video. The troubleshooting steps are similar but use Pipewire utilities.

5.1 Install Pipewire and Related Packages

If Pipewire is not installed, install it:

sudo apt install pipewire pipewire-pulse wireplumber

Restart Pipewire:

systemctl --user restart pipewire
systemctl --user restart pipewire-pulse

5.2 Confirm the Source with pw-cli

List all sources:

pw-cli ls Node | grep -i mic

You should see a node named something like alsa_input.usb-Logitech_C930-01-analog-stereo. Note its id.

5.3 Test with pw-record

Record a few seconds:

pw-record --duration 5 test.wav

Play back:

pw-play test.wav

If you hear audio, the device works under Pipewire. If not, try specifying the device directly:

pw-record --card 1 --device 0 test.wav

5.4 Configure Application Settings

Applications that use Pipewire (e.g., OBS, Discord, Zoom) should automatically detect the webcam microphone. In OBS, go to Settings > Audio and set the Mic/Auxiliary Audio Device to alsa_input.usb-Logitech_C930-01-analog-stereo. In Zoom, go to Settings > Audio and select the same source.

If your application still does not see the microphone, try restarting the application after confirming that the Pipewire source appears in the list above.

6. Advanced Troubleshooting

If the steps above do not resolve the issue, proceed to deeper diagnostics.

6.1 Kernel Upgrade

Older kernels may lack full support for newer USB audio devices. Check your current kernel:

uname -r

If you are running a kernel older than 5.10, consider upgrading to a newer one available from the Linux Mint repositories or from the official Ubuntu releases. For example:

sudo apt update
sudo apt full-upgrade
sudo reboot

After reboot, repeat sections 2 and 4 or 5.

6.2 Verify the Module Parameters

The snd_usb_audio module has several parameters that can influence device detection. Check the current parameters:

modinfo snd_usb_audio

If you suspect a parameter issue, you can add a custom udev rule:

sudo nano /etc/udev/rules.d/99-logitech-c930.rules

Insert:

ATTRS{idVendor}=="046d", ATTRS{idProduct}=="08d5", RUN+="/sbin/modprobe snd_usb_audio"

Reload udev:

sudo udevadm control --reload-rules
sudo udevadm trigger

6.3 Use ffmpeg for a Quick Test

ffmpeg can read from ALSA devices and provide detailed output:

ffmpeg -f alsa -i hw:1,0 -t 5 -f null -

If ffmpeg reports No such device, the audio device is still not exposed correctly.

6.4 Inspect dmesg for USB Audio Errors

Run:

dmesg | grep -i 'snd_usb_audio'

Look for lines such as:

snd_usb_audio 0000:00:14.0: USB audio device (model Logitech C930) not found

If you see such errors, the device may not be fully compatible with the current driver. Search for any known bugs in the Ubuntu Bug Tracker or on Logitech’s support site.

6.5 Verify Permissions of /dev/snd/

The audio devices live under /dev/snd/. Ensure they are world‑readable or that your user has the correct group membership:

ls -l /dev/snd

Typical output:

crw-rw-r-- 1 root audio 116, 0 Oct 10 12:34 controlC1
crw-rw-r-- 1 root audio 116, 2 Oct 10 12:34 pcmC1D0c

If the permissions are restrictive, modify them with:

sudo chgrp audio /dev/snd/*
sudo chmod g+rw /dev/snd/*

7. Configuring Applications to Use the Webcam Microphone

Once you have confirmed that the system can capture audio from the Logitech C930, you need to tell your chosen application to use that source.

7.1 OBS Studio

1. Open Settings > Audio.
2. Under Mic/Auxiliary Audio Device, choose the entry that matches the webcam microphone (alsa_input.usb-Logitech_C930-01-analog-stereo for Pipewire or hw:1,0 for PulseAudio).
3. Click Apply.
4. In the main OBS window, press Start Streaming or Start Recording to test.

7.2 Zoom

1. Go to Settings > Audio.
2. Under Microphone, select the webcam mic.
3. Mute and unmute to confirm sound is coming through.

7.3 Discord

1. Open User Settings > Voice & Video.
2. In Input Device, pick the webcam microphone.
3. Use the Test Your Mic button to check.

7.4 Gnome / KDE Sound Settings

For a global system setting, open your desktop environment’s sound control panel, go to the Input tab, and select the webcam mic. Some environments expose the device as Logitech C930 Microphone or USB Audio (Logitech C930).

8. Workarounds If All Else Fails

If, after exhaustive testing, the Logitech C930 microphone still fails to work, consider the following practical workarounds.

8.1 Use a Dedicated USB Microphone

A dedicated USB mic offers superior audio quality and is often easier to configure. Many low‑cost options (<$50) deliver clear sound and plug straight into the same USB port.

8.2 Use an External Audio Interface

If you already own a USB audio interface (such as the Focusrite Scarlett 2i2), connect a standard XLR or TRS mic. The interface will expose a reliable audio device to the OS.

8.3 Switch to a Different Web Camera

Some alternative webcams (e.g., Logitech C920, C920s, or the newer Brio) have better Linux support. If your workflow permits, swap the hardware.

8.4 Reinstall the Operating System

In rare cases, a corrupted installation of the ALSA or PulseAudio stack can cause subtle issues. Back up your data, reinstall Linux Mint, and follow the steps above fresh. This often resolves unseen conflicts.

9. Summary

1. Hardware Check – Ensure the webcam is physically connected to a healthy USB port.
2. Kernel Recognition – Use lsusb, arecord -l, and dmesg to verify the device is seen by the kernel.
3. Group Membership – Add your user to audio and video groups.
4. PulseAudio – Load the ALSA source module, test with arecord, and confirm the source in pavucontrol.
5. Pipewire – Use pw-cli, pw-record, and confirm the source in the application.
6. Advanced Diagnostics – Upgrade the kernel, add udev rules, inspect dmesg, use ffmpeg.
7. Application Configuration – Point OBS, Zoom, Discord, or system sound panels to the webcam mic.
8. Workarounds – If the microphone remains silent, consider an external mic or a different webcam.

By systematically following these steps, you should be able to restore audio capture from your Logitech C930 on Linux Mint. The process also gives you a deeper understanding of how Linux interacts with USB audio devices, empowering you to troubleshoot future hardware problems.

If you encounter any specific error messages during these steps, feel free to search the Linux Mint forums, Ubuntu Bug Tracker, or Logitech’s support page for additional clues. Good luck and happy recording!