Setup Guide for MuteMe on Linux Systems
MuteMe · Setup & support
Set up MuteMe on Linux
Use the app’s Linux setup checks to configure USB access and select the audio system already in use on your computer.
- Release channel
- Linux beta
- Audio
- Auto Detect / PipeWire / PulseAudio
- Installers
- DEB and RPM
Install the package for your distribution
Choose the Linux DEB or RPM package from Downloads. Read the current compatibility notes there. Linux does not use the app’s automatic-update flow; install a newer package when you update.
Earlier MuteMe testing listed Ubuntu 20.04, 24.04 and 24.10, plus Fedora 40. Those are historical tested versions, not a promise that every distribution or future release behaves identically.
Let the app detect your audio stack
Do not replace a working PipeWire installation with a PulseAudio daemon just because an older guide says to install PulseAudio. PipeWire can provide PulseAudio compatibility.
Start with Auto Detect
In the app’s Linux Setup panel, use Auto Detect (Recommended). Select PipeWire or PulseAudio only when you know which audio system your computer uses.
Run the guided checks
Follow the setup prompts for required audio tools and USB access. The panel provides Run Linux Setup Checks Again and Open Linux Setup Guide if a check needs another attempt.
Test your selected microphone
Choose the microphone in MuteMe and in your meeting app. Check mute and unmute on that exact input. A working Linux audio service and permission to control it are both needed.
Approve the USB setup when prompted
If MuteMe shows Linux USB Access Setup, follow Continue and the administrator prompt to let its setup helper install device-access rules. If it identifies outdated rules, review its Update Rules prompt. Run MuteMe normally; the setup helper requests elevated permission for the system change.
Current generated rules use /etc/udev/rules.d/69-muteme.rules, device-specific IDs, MODE="0660" and TAG+="uaccess". The helper also handles an available device-access group. If it reports a group membership change, sign out and back in, then reconnect the device and retry.
On a managed computer, ask your administrator to approve the device-access change. Do not use the older world-writable rule block below as a substitute for the current setup helper.
Understand the Linux integration limits
OS microphone control and meeting-app synchronization are different. The released app lists OBS Studio as a Linux desktop integration and Google Meet as a web integration. Use their OBS and Google Meet guides; do not assume that every Windows or macOS integration has a Linux equivalent.
If several MuteMe devices are connected, describe the exact models and behavior when contacting Support. Follow the multi-device guide and confirm your exact combination before deploying it.
Collect a useful diagnosis
Tell Support your distribution and version, desktop session, selected audio stack, package type, device model and the failing setup check. If the relevant tools are already installed, these read-only commands can help identify the active audio service:
wpctl status
pactl infoA missing command is diagnostic information; it does not mean you should install or replace an audio server indiscriminately.
Reference for older installations
Historical manual commands from the 2024 guide
Reference only: these commands are retained to help identify an old installation. They create broader device permissions and assume a PulseAudio setup. Prefer the current app’s generated rules and detected audio stack; do not paste this sequence over a working modern setup.
sudo nano /etc/udev/rules.d/99-muteme.rulesSUBSYSTEM=="usb", ATTRS{idVendor}=="20A0", ATTRS{idProduct}=="42DB", MODE="0666", GROUP="plugdev"
KERNEL=="hidraw*", ATTRS{idVendor}=="20A0", ATTRS{idProduct}=="42DB", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="20A0", ATTRS{idProduct}=="42DA", MODE="0666", GROUP="plugdev"
KERNEL=="hidraw*", ATTRS{idVendor}=="20A0", ATTRS{idProduct}=="42DA", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="3603", ATTRS{idProduct}=="0001", MODE="0666", GROUP="plugdev"
KERNEL=="hidraw*", ATTRS{idVendor}=="3603", ATTRS{idProduct}=="0001", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="3603", ATTRS{idProduct}=="0002", MODE="0666", GROUP="plugdev"
KERNEL=="hidraw*", ATTRS{idVendor}=="3603", ATTRS{idProduct}=="0002", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="3603", ATTRS{idProduct}=="0003", MODE="0666", GROUP="plugdev"
KERNEL=="hidraw*", ATTRS{idVendor}=="3603", ATTRS{idProduct}=="0003", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="3603", ATTRS{idProduct}=="0004", MODE="0666", GROUP="plugdev"
KERNEL=="hidraw*", ATTRS{idVendor}=="3603", ATTRS{idProduct}=="0004", MODE="0666", GROUP="plugdev"sudo udevadm control --reload-rules && sudo udevadm triggersudo apt-get install pulseaudio -ysudo dnf install pulseaudio pulseaudio-utils -yEarlier Linux interface
We’re here to help
Still need a hand?
The best way to contact us is through the Support tab in the MuteMe app. Include your device, operating system, app version and what you have already tried.