SUMMARY When launching "Sound" in System Settings, there appears to be no "Configure..." button available. This button is required to enable functions such as the creation of a Virtual device for simultaneous sound output. In reality, the button exists, but is covered by the other buttons "Rename Devices..." and "Configure Volume Controls...". You can briefly observe it in a grayed out state upon initial loading of the "Sound" module, but then the other buttons cover it. STEPS TO REPRODUCE 1. Open System Settings 2. While looking at the upper right area of System Settings, click on "Sound" OBSERVED RESULT "Configure..." briefly appears in a grayed out state and then is covered by the other buttons. EXPECTED RESULT The "Configure..." button should remain visible and be selectable. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDENeon 6.2 User Edition KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Linux/KDE Plasma: KDE Linux 202411230401 KDE Plasma Version: 6.2.80 KDE Frameworks Version: 6.9.0 Qt Version: 6.8.0 Linux/KDE Plasma: Kubuntu 24.10 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.6.2
What do you mean by covered? Can you attach a screenshot or a screen recording that shows the issue?
(In reply to Nate Graham from comment #1) > What do you mean by covered? Can you attach a screenshot or a screen > recording that shows the issue? I mean the button VERY briefly appears in the upper right corner then the other two buttons slide in from the right and cover the Configure... button. It's easily reproducible, but not easily captured. I'll try.
Created attachment 176140 [details] short screen cap of Capture button disappearing Capture from Kubuntu 24.10
Sorry "Configure..." button disappearing
Thanks for the screen recording. Its very odd, and I can't reproduce it. I'll have to look at the code to see what in principle might be happening.
Ah, I see what's happening. We do have a secret "Configure" button, that appears and disappears based on the following condition: > visible: moduleManager.settingsSupported So clearly what's going on here is that this property is briefly set to true when the page loads, then becomes false. Testing again, I can reproduce it now. It only happens on the *first* time the KCM loads when System Settings is open. I didn't see it last time because System Settings must have already been open with me having opened the KCM at least once before.
Thanks for digging in and confirming. It's appreciated.