Bug 449640

Summary: System Settings: Audio list of profiles list is too narrow
Product: [Applications] systemsettings Reporter: Bardur Arantsson <bugs-kde.org>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bugseforuns
Priority: NOR    
Version: 5.23.5   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Screen shot

Description Bardur Arantsson 2022-02-05 08:51:44 UTC
In the Audio settings, the drop-down list of audio profiles doesn't have enough space horizontally, so it gets cut off -- making it impossible to distinguish the profiles in certain cases.

STEPS TO REPRODUCE
1. Open Audio settings
2. Click the Profile drop-down

OBSERVED RESULT

If you have similar devices to me, you'll observe that the there are multiple entries that look exactly the same because they've been shortened. (See attached screenshot)

EXPECTED RESULT

The list should be wide enough to show the full names.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Comment 1 Bardur Arantsson 2022-02-05 08:52:36 UTC
Created attachment 146300 [details]
Screen shot
Comment 2 Bardur Arantsson 2022-02-05 08:57:32 UTC
Huh, right after reporting I see that the behavior of the profile drop-down is pretty weird. It *starts* in this state of being too narrow, but if I select a specific device it'll (for some reason) limit to a certain subset of devices and won't show the full list.

If I then click to a different settings "plugin" e.g. Power Management and back to Audio, the drop-down is resized and shows the full list.

(Sorry, it's a bit hard to describe, but something's definitely wonky about that drop-down. If that was too hard to follow I can try to record a video, do let me know if one is necessary. I don't really know screen recording software, but I can probably get something up and running if needed :) .)
Comment 3 Patrick Silva 2022-02-05 14:42:26 UTC

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