Hi,
I’m experiencing an issue recording system audio (Eg recording YouYube) on CachyOS using a Sound Blaster AE‑5 Plus (CA0132). After updates around 2026‑03‑27, all PortAudio‑based applications (Audacity, Tenacity, etc.) now show ALSA‑only devices and no longer expose PulseAudio/PipeWire monitor sources. This makes system‑audio capture impossible on CA0132 hardware, which does not provide hardware monitor capture via ALSA.
The timing coincides with the upgrade of:
portaudio 1:19.7.0‑3.2 → 1:19.7.0‑4.1
Packager: CachyOS admin@cachyos.org
Installed From: cachyos-extra-v3
Build Date: 19 Mar 2026
This build does not list libpulse as a dependency, which may indicate that the PulseAudio backend was not compiled (Or something else was missed out) However, I cannot confirm whether this is the root cause or just a correlation.
Additional context:
-
PipeWire‑Pulse itself is functioning normally.
-
The issue affects the AE‑5 Plus specifically; onboard Realtek output appears unaffected (likely because they still have ALSA capture paths).
-
Flatpak Audacity shows identical behaviour, suggesting the problem is at the host‑audio level rather than the application.
-
The same workflow works correctly on Linux Mint with the same hardware.
-
KDE’s KWave, which does not use PortAudio and records directly via ALSA, can record system audio normally. This suggests the issue is limited to software relying on the PortAudio/PulseAudio backend path.
I’m not certain whether the issue originates from PortAudio, PipeWire, the CA0132 driver, or a combination of factors. I’m raising this because the behaviour changed immediately after the March update, and the AE‑5 Plus relies heavily on PulseAudio monitor nodes for system‑audio capture.
Any guidance on whether this is a packaging issue, or something else would be much appreciated.
Thanks.