Bug 460388

Summary: Opening then closing widget does not remove created node from Pipewire, leading to multiple "Plasma PA" dangling nodes
Product: [Unmaintained] plasma-pa Reporter: bird_d <relay198>
Component: appletAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: andrej.halv, kde, nate, nicolas.fella, nowrep, sitter
Priority: NOR    
Version First Reported In: 5.26.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Picture of dangling Plasma PA nodes in both Helvum and qpwgraph

Description bird_d 2022-10-13 19:54:34 UTC
Created attachment 152789 [details]
Picture of dangling Plasma PA nodes in both Helvum and qpwgraph

SUMMARY
Using Pipewire, the Volume Audio widget (Plasma PA) does not remove itself from the graph it seems, but always creates a new node when it is activating. If you were to quickly toggle it over and over, you will end up having many nodes called "Plasma PA" created.
I have not tested Pulseaudio, so I am unsure if it happens there in some way.


STEPS TO REPRODUCE
1. Open some sort of Pipewire graph (Helvum / qpwgraph / pw-viz) to observe. They also show up with `pw-cli list-objects Node`.
2. Open the widget
3. Close the widget

OBSERVED RESULT
    Some nodes get destroyed, but there is one node that doesn't.

EXPECTED RESULT
    The "dangling" node should be destroyed with the others.

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6
Kernel Version: 6.0.1-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 1700 Eight-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7B79
System Version: 3.0

ADDITIONAL INFORMATION
pipewire --version
pipewire
Compiled with libpipewire 0.3.59
Linked with libpipewire 0.3.59
Comment 1 Nate Graham 2022-10-14 19:11:03 UTC
Can reproduce.
Comment 2 Andrej Halveland 2023-08-13 23:03:12 UTC
I believe this is the same behavior as in my own bug report? https://bugs.kde.org/show_bug.cgi?id=467117
Comment 3 Harald Sitter 2024-10-03 12:07:36 UTC

*** This bug has been marked as a duplicate of bug 467117 ***