Bug 484662 - Profiles controlling device capabilities is confusing
Summary: Profiles controlling device capabilities is confusing
Status: CONFIRMED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_pulseaudio (other bugs)
Version First Reported In: 6.0.3
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: usability
: 514038 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-03-28 13:13 UTC by Andreas
Modified: 2026-01-06 21:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas 2024-03-28 13:13:57 UTC 
SUMMARY

I may not be aware of all use cases, but the selection of the profile in the Sound dialog of the systemsettings app appears to be counter-intuitive. 
Based on tests of the interface and comparison to pavucontrol, the selection of a "Profile" determines which Input and Playback Devices etc. are active. 
Since the dropdownlist appears in general repeatedly, for each device or device type, placed behind the "Port" of the device, the global role of the function is not represented well in the GUI:
Switching the profile will affect all devices. 
It appears that it would better appear only once and be placed above the listing of the device types.
Also, "Input Devices" may better correspond to the user's expectation than "Recording Devices".       

STEPS TO REPRODUCE
1. Start systemsettings.
2. Go to "Input & Output" -> "Sound"
3. Observe the GUI
Comment 1 Nate Graham 2026-01-06 21:51:36 UTC 
*** Bug 514038 has been marked as a duplicate of this bug. ***