How to Read WirePlumber Logs

Before you start

WirePlumber logs come from the WirePlumber session manager running on the local system. You must be able to run commands on that machine, either in a terminal or over a secure shell session. On most current Linux systems using PipeWire, WirePlumber is already active as a user service; you do not need to stop it just to read its recent output.

Step-by-step instructions

First open a terminal and run the command available on your system:

journalctl --user -u wireplumber -e

The -e option jumps to the end of the log, which is useful when you have just tried to use a camera, microphone or audio device and want to see the most recent activity. If you need older entries, remove -e and page through the output.

For more details, temporarily change the log level with:

systemctl --user edit wireplumber

In the editor, create or extend the service section so the service starts with a level such as 4 or 5:

[Service]
Environment=WIREPLUMBER_DEBUG=4

Then restart the service:

systemctl --user restart wireplumber

The exact variable and service name can differ between WirePlumber versions and distributions. If WIREPLUMBER_DEBUG produces no extra output, remove the temporary change rather than adding more overrides blindly.

Check the output

After reproducing the problem with the camera, microphone or audio device, open the log again. Look for entries mentioning the device node, stream or profile. Timestamps show the order of events, but log detail is not a guarantee that every device error will be described accurately; some messages report the session manager's view of an event rather than a complete hardware diagnosis.

To reduce noise while checking, follow the newest entries in real time during a short test:

journalctl --user -u wireplumber -f

Common problems and next steps

If a device keeps appearing and disappearing in the log, check whether it is being claimed by another session or whether USB power management is affecting it. If the log stops unexpectedly, confirm that the wireplumber service is still running with:

systemctl --user status wireplumber

After troubleshooting, return the service to its normal log level or remove the override. Keeping a high debug level can create large logs and reduce performance. Once the output is readable, use it to identify the failing device or stream, which is usually the first step before changing audio or video settings.