How to Open pavucontrol from Waybar

Before you start

This procedure runs locally on a Linux system using Waybar. It assumes PulseAudio or PipeWire with the PulseAudio compatibility layer is active, because pavucontrol is a PulseAudio volume control client. Check that pavucontrol is installed and launchable from a terminal before adding it to Waybar. The action itself does not need a remote service.

Step-by-step instructions

One direct method is to configure a custom Waybar module with an on-click action. Open the Waybar configuration file in a text editor. Locate the bar module named custom/pavucontrol or create a new custom module in the modules section.

"custom/pavucontrol": {
    "format": "Volume",
    "on-click": "pavucontrol"
}

Add the new module name to the desired position in the modules-left, modules-center, or modules-right list. For example, place custom/pavucontrol near a clock or tray module.

Save the file and reload Waybar. Depending on the installed version and launch method, reload may happen automatically, or you can kill the running Waybar process and start it again.

An alternative is to add the command to an existing module tray with a suitable click handler, if that module accepts an on-click action. Not all tray implementations expose click commands, so a dedicated custom module is usually more predictable.

Check the output

Click the new Waybar item and verify that the pavucontrol window appears. The window should show tabs or controls for playback devices, recording devices, output devices, input devices, and configuration, depending on the installed version and available audio hardware.

If the window does not open, run pavucontrol from a terminal. An error such as a missing binary or an audio connection failure points to the underlying cause. A successful launch from Waybar means the module is configured correctly, not that any particular microphone or camera device is working.

Common problems and next steps

If Waybar reports an unknown module, check that the custom module name is spelled consistently in the modules section and the placement list. A missing or mistyped name prevents the item from appearing.

If clicking the item does nothing, confirm that the configuration file loaded the edited section and that the on-click value is quoted as a single command. Some Waybar versions may require a command without an absolute path, while others may perform better with a full path to pavucontrol. Run command -v pavucontrol to find its location if needed.

If pavucontrol opens but does not show devices, verify which audio server is running. With PipeWire, pavucontrol normally shows devices only when pipewire-pulse is active. Checking the active server can be done with the relevant terminal utilities for your distribution, without assuming that missing controls mean a broken camera or microphone.

These changes are reversible. To stop using the item, remove the custom module from the placement list or delete the module definition, then reload Waybar. Pavilion changes made through pavucontrol last as long as the audio session or saved configuration allows; reconnecting or rebooting may apply previously selected device settings again.