Created attachment 147304 [details] Screenshot 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 *** I'm using pipewire(-pulse), which may or may not matter. But, after logging in from a fresh boot, plasma displays a "Built-In Audio Analog Stereo" pop-up for a few seconds. This feels like a "papercut" bug that should be hidden? STEPS TO REPRODUCE 1. Fresh boot 2. Login, view pop-up 3. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.13.3
Hmm it already tries to avoid the transition from no sink to default sink as it starts up [1]. Perhaps with pulseaudio we're seeing a transition from no sink → pulse dummy sink → pipewire sink? [1] https://invent.kde.org/plasma/plasma-pa/-/blob/master/applet/contents/ui/main.qml#L220
On my system, it also pops up when it resumes from suspend. My system (Fedora 36 KDE) utilises Pipewire as well, so I think this bug is related to it. Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0
Unlike the legacy PulseAudio, PIpeWire initializes as quickly as possible and then does asynchronous device discovery. This itself is, I'd guess, invisible in terms of popups. What, I expect, is most likely generating the popups is the default sink change as higher priority sinks are discovered and become the new default until either the initial device discovery is done or PW finds the user chosen default sinks (what pavucontrol oddly denotes as fallback) at which point it will stay with that device until the user changes the default sink or the device disappears and the PW session manager picks the next default in the order of the configured priority. If my suspicious are correct, then the popups will keep happening unless the discovered device is also the user preferred default sink (or there's no more non-default sinks to discover). And because it could be set in some other way than via plasma-pa (meaning one should not rely on prior knowledge of previous plasma-pa default sink state), I'm not sure if there's an easy and quick to check way to know if the default sink change flurry is over (but I'm not expert on the PulseAudio API, so maybe there is one?). A less reliable method would be to just suppress all such events for a set time after login, resume and possibly session and/or tty switch.
Is this still a problem?
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
(In reply to Harald Sitter from comment #4) > Is this still a problem? Yes, this issue can be reproduced on different systems running Plasma 6.0 and 6.1 with pipewire (some display the volume level, others the output device) Please let me know if additional information is required.
how about 6.2 :D
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
(In reply to Harald Sitter from comment #7) > how about 6.2 Can confirm the same issue with Plasma 6.2.4
This issue persists in KDE Plasma Version 6.3.2 and KDE Frameworks Version 6.11.0