Created attachment 160858 [details] screenshot of duplicate devices in applet SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Issue appeared after switching from alsa to wireplumber pipewire pipewire-pulse i am not entirely sure if this is an issue with the applet. however i only observe one device in the audio section of system settings as expected. Audio in system settings shows only one device, while applet shows a device for each reconnect. i have only been able to test with sony WH-1000XM5 using void-linux STEPS TO REPRODUCE 1. using paired headset, power on headset and wait for automatic connection. 2. after connection has been established and device is shown in applet, power off headset 3. power on headset, wait for reconnect, close and open applet, it should then show 2 devices. OBSERVED RESULT duplicate devices are shown media keys can only change between e.g. 29% and 39% volume and have no effect on actual volume changing the volume of the last(bottom) device in the list changes the volume of the device. EXPECTED RESULT only active devices are shown. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.7 Linux: 6.4.8_1 (mainline void linux) ADDITIONAL INFORMATION
Seems to happen for any audio device being removed and re-added. Same as bug 473177 ?
(In reply to Martin from comment #1) > Seems to happen for any audio device being removed and re-added. Same as bug > 473177 ? Yes i believe it is. it was no able to find the similar report, i will look more closely next time :)
(In reply to Martin from comment #1) > Seems to happen for any audio device being removed and re-added. Same as bug > 473177 ? Yes i believe it is. it was no able to find the similar report, i will look more closely next time :) https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3414
*** This bug has been marked as a duplicate of bug 473093 ***