Bug 504640

Summary: Duplicate Selected Radio Button in KDE Audio Device Selection
Product: [Plasma] plasmashell Reporter: Anton Valishin <anton>
Component: Audio Volume widgetAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: isma.af, kdedev, nate
Priority: NOR    
Version First Reported In: 6.3.5   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Video showing bug

Description Anton Valishin 2025-05-21 22:41:05 UTC
Created attachment 181628 [details]
Video showing bug

SUMMARY
In the KDE audio device selection interface, the radio button for the output device "UGREEN-70304" appears selected twice, while "Built-in Audio Digital Stereo (HDMI)" is not selectable. This visual bug prevents proper audio output switching.

STEPS TO REPRODUCE
1. Switch audio outputs
2. 
3. 

Operating System: Fedora Linux 42
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.6-300.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 32 × 13th Gen Intel® Core™ i9-13900K
Memory: 94,0 GiB of RAM
Graphics Processor: Intel® Graphics
Manufacturer: ASUS
Comment 1 TraceyC 2025-05-22 00:31:43 UTC
From the video, it appears that "UGREEN-70304" is selected *once* not twice
*and* that clicking on "Built-in Audio Digital Stereo (HDMI)" selects that as well, so both devices are selected.

The visual bug I see is that both the UGREEN and HDMI audio device radio buttons are selected, when only one should be able to be selected
Clicking on the HDMI output should un-select the UGREEN output
Comment 2 Anton Valishin 2025-05-22 00:38:36 UTC
(In reply to TraceyC from comment #1)
Correct
Also 
1 Ugreen selected 
2 click to HDMI 
3 click to Ugreen (HDMI remains selected)
4 hit enter on keyboard: it unselects HDMI
Comment 3 TraceyC 2025-05-22 00:48:32 UTC
I'm pretty sure I saw this yesterday on 6.3.5, but I can't reproduce today on that version or git-master. I'll leave this open in case someone else can reproduce.
Comment 4 Anton Valishin 2025-05-22 02:49:12 UTC
(In reply to TraceyC from comment #3)
> I'm pretty sure I saw this yesterday on 6.3.5, but I can't reproduce today
> on that version or git-master. I'll leave this open in case someone else can
> reproduce.

Here is gdb core dump (gcore)
gdb --args plasmashell -d --replace
on breakpoint Sink::setDefault
when the bug appers
https://drive.google.com/drive/folders/14uJsbl0K6RDLNvy7xo8ggq8x5aMNjHsT
Comment 5 Anton Valishin 2025-05-22 14:05:40 UTC
(In reply to TraceyC from comment #3)
> I'm pretty sure I saw this yesterday on 6.3.5, but I can't reproduce today
> on that version or git-master. I'll leave this open in case someone else can
> reproduce.

I was able to reproduce it with the latest neon-unstable-developer-20250512-0038
I have a QEMU VM with a snapshot during bug (CPU is set to qemu64)

https://drive.google.com/drive/folders/14uJsbl0K6RDLNvy7xo8ggq8x5aMNjHsT
virsh snapshot-create --domain linux2024 --redefine snapshot2.xml

so coredump is deleted from gdrive
Comment 6 Nate Graham 2025-05-22 15:53:45 UTC

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