Bug 514038 - Confusing / error prone user interface for pipewire audio profiles
Summary: Confusing / error prone user interface for pipewire audio profiles
Status: RESOLVED DUPLICATE of bug 484662
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_pulseaudio (other bugs)
Version First Reported In: 6.5.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-01 12:52 UTC by Vorpal
Modified: 2026-01-06 21:51 UTC (History)
3 users (show)

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


Attachments
Screenshots showing the confusion (30.75 KB, image/png)
2026-01-01 12:52 UTC, Vorpal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vorpal 2026-01-01 12:52:59 UTC
Created attachment 188131 [details]
Screenshots showing the confusion

SUMMARY

In the KDE Systems Settings on the Sound page, there is a drop down *per input/output device* for the "Profile", with values such as "Analog Stereo Duplex". The UI here is confusing, as this setting really isn't per device, but tied together. For example: changing "Analog Stereo Duplex" on the laptop speakers output to "Analog Stereo Output" *removes* the "Internal Microphone" input. If you happen to change this by mistake, it isn't obvious that you need to change a setting on your speakers to get your microphone back. See attached screenshots.

Contrast this with pavucontrol, where the profile setting for "Built in Audio" is on a separate tab entirely, and not duplicated twice. This makes it more obvious that it is a setting that might be relevant to your troubleshooting.

I would recommend that the profiles are moved into a separate section from the devices, since there isn't a 1:1 mapping and entries can appear and disappear randomly as you change profile.

STEPS TO REPRODUCE
1. Change profile in sound settings
2. Become very confused when your microphone disappears and you can't find where to re-enable it.
3. End up filing a pipewire bug report (https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/5051), even though it was just confusing UX.

OBSERVED RESULT
Inputs disappear in the list and it isn't obvious that you need to change a setting on an output (which is working) to get things fixed.

EXPECTED RESULT
A less confusing user experience.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1

ADDITIONAL INFORMATION
Comment 1 David Edmundson 2026-01-02 10:25:46 UTC
I agree the UX isn't perfect; though hiding it all away isn't great either.

Being able to switch bluetooth headsets between sounding good and working as a headset needs to be very quickly without additional hoops. 
It's not a simple fix.
Comment 2 Nate Graham 2026-01-06 21:51:36 UTC

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