Summary: | Visual feedback of currently playing audio in plasma-pa with pipewire breaks bluetooth headset power management and pipewire adaptive sample rate | ||
---|---|---|---|
Product: | [Plasma] plasma-pa | Reporter: | Dmitrii Chermnykh <chermnykh2001> |
Component: | applet | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | CONFIRMED --- | ||
Severity: | minor | CC: | chermnykh2001, isma.af, me, nate, nowrep |
Priority: | NOR | ||
Version: | 5.27.9 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Dmitrii Chermnykh
2023-11-25 20:18:08 UTC
After restarting `plasmashell` the `Plasma PA` client disappears from `pw-top` which fixes low power state for bluetooth devices and pipewire sample rate switch On the pipewire graph there is a virtual `plasma pa` node which gets created and automatically connected to every `monitoring` port when plasma-pa widget is first opened Seems like the are couple of lifetime bugs. First, depending on whether the applet is in system tray or not, it may fail to clean up its nodes when full representation is closed: Applet in system tray behaves better than a standalone on a panel. Second, the system tray applet may fail to clean up nodes of a paused playback stream. I have an mpv playing some music, and each time I open Audio applet in system tray, I see a new "Plasma PA" node being created in pw-top. They keep stacking up until I close mpv or restart Plasma. Interestingly, standalone applet does not exhibit such an issue. I filed an upstream bugreport to speech-dispatcher because their streams are getting stuck in limbo PA_STREAM_CREATING state causing leaks in my case. I assume there might be more apps out there that create buggy streams, which we can not immediately disconnect (because the rules) and which can not be disconnected later via state change callback (because state never changes). https://github.com/brailcom/speechd/issues/871 Found another closely related upstream bug report in pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2168 So is it purely an upstream bug? Or do we think there's anything we can do here? (In reply to Nate Graham from comment #6) > So is it purely an upstream bug? Or do we think there's anything we can do > here? I think we can delete and then recreate plasma-pa node as a workaround |