https://bugs.kde.org/show_bug.cgi?id=438565
--- Comment #10 from nyanpasu64 <nyanpas...@tuta.io> --- On Arch Linux, I'm experiencing this bug with pipewire, pipewire-pulse, and pulseaudio-alsa installed. This means plasmashell is using the Pulse(?) API to talk to pipewire, and ALSA apps are using pulseaudio-alsa to speak Pulse to pipewire-pulse/pipewire (rather than speaking ALSA to pipewire). It appears that somewhere in the multiple layers of shims, the "app playing audio" information gets lost. I can't run pacmd easily, since that ships with the pulseaudio package, which conflicts with pipewire-pulse. * If I extract the pulseaudio package and run pacmd with pipewire-pulse running (but not pulseaudio), I get "No PulseAudio daemon running, or not running as session daemon." * If I remove pipewire-pulse and install pulseaudio (but leave pipewire installed), then Pipewire is effectively disabled and this bug no longer occurs. If I install pipewire-alsa and uninstall pulseaudio-alsa (with either pulseaudio or pipewire-pulse installed/running), now ALSA apps are using pipewire-alsa to talk directly(?) to pipewire. I no longer get volume keys in the task manager. `aplay /dev/urandom` works, Audacity works, but RtAudio apps (BambooTracker, exotracker) hang and burn CPU instead of playing audio properly. I can debug this if desired. Should I report a bug at RtAudio or PipeWire? Or debug first and then report a bug? -- You are receiving this mail because: You are watching all bug changes.
