Hi everyone,

I’m trying to understand a PipeWire/WirePlumber issue I encountered and would appreciate your insights.

* Summary of the issue

After installing pavucontrol, my system began experiencing:

Audio breaking completely
OBS crashing (/usr/bin/obs fatal error)
Firefox freezing
KDE Plasma becoming unresponsive

Initially, I assumed this was caused by pavucontrol, but further testing suggests it only triggered a deeper issue.

*Hardware involved

The problematic device appears to be the following webcam:

Brand: Aicoco
2K Webcam with AI tracking and dual microphones (USB)

Before installing pavucontrol, this webcam worked without any noticeable issues in OBS and general usage.

* What I discovered

After debugging:

Rolling back / and /home via Snapper partially improved stability
However, the issue persisted
The system immediately became unstable when plugging in the Aicoco webcam

When I unplug the webcam:

Audio works perfectly
OBS launches instantly
KDE and Firefox behave normally

Other devices (Insta360 Link webcam, OBS virtual camera) work without issues.

* Relevant logs (WirePlumber)

From:

journalctl --user -xeu wireplumber.service

I consistently get:

wp-device: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
PipeWire's libcamera SPA plugin is missing or broken. Some camera types may not be supported.

Object activation aborted: proxy destroyed

link failed: some node was destroyed before the link was created

1 of 1 PipeWire links failed to activate

* Interpretation (my current understanding)

It seems:

The webcam exposes both video and audio interfaces
WirePlumber attempts to initialize it (possibly via libcamera)
The device fails during activation (node destroyed mid-process)
PipeWire graph linking fails
This causes cascading issues:
audio graph instability
OBS crashes
applications freezing or blocking

* Questions
Is this a known issue with certain USB webcams and PipeWire/libcamera?
Why would the device behave normally before installing pavucontrol, but fail afterward?
Is the “libcamera SPA plugin missing or broken” message expected on Arch, or should I install additional packages?
Would it be better to:
disable libcamera integration entirely?
or block the webcam’s audio interface?
Is there a recommended way to prevent a faulty device from destabilizing the entire PipeWire graph?

* Additional notes
System: Arch Linux (fully updated)
Audio stack: PipeWire + WirePlumber
Issue is 100% reproducible when plugging that specific webcam
Other cameras and audio devices behave normally

Thanks in advance — I’m mainly trying to understand whether this is:

a configuration issue
missing components (libcamera SPA)
or simply hardware incompatibility