Bug 499023

Summary:	Implement support for resetting applicable settings to their default values, and the "Highlight Changed Settings" feature
Product:	[Applications] systemsettings	Reporter:	Roke Julian Lockhart Beedell <4wy78uwh>
Component:	kcm_pulseaudio	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	nate
Priority:	NOR
Version First Reported In:	6.2.5
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
URL:	https://discuss.kde.org/t/can-the-volume-of-system-sounds-be-controlled/28658/3?u=rokejulianlockhart
See Also:	https://bugs.kde.org/show_bug.cgi?id=490953 https://bugs.kde.org/show_bug.cgi?id=499037
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Demonstration screenshot for `#c0`. The latest version of the report, because BZ doesn't support post edits.

Description Roke Julian Lockhart Beedell 2025-01-22 19:14:22 UTC

Created attachment 177600 [details]
Demonstration screenshot for `#c0`.

SUMMARY
-------

The "Highlight Changed Settings" preference does not apply to the "PulseAudio" KCM's stream-specific volume-sliders.

STEPS TO REPRODUCE
------------------

1. ~~~sh
   #!/usr/bin/env sh
   systemsettings
   ~~~

2. Enable "Highlight Changed Settings".

3. ~~~sh
   #!/usr/bin/env sh
   systemsettings kcm_pulseaudio # *Not* `kcmshell6`
   ~~~

4. Modify the volume of a stream.

OBSERVED RESULT
---------------

The volume slider does not become orange.

EXPECTED RESULT
---------------

It should.

SOFTWARE/OS VERSIONS
--------------------

1. ~~~sh
   #!/usr/bin/env sh
   kinfo
   ~~~

2. > ~~~sh
   > Operating System: Fedora Linux 41
   > KDE Plasma Version: 6.2.5
   > KDE Frameworks Version: 6.10.0
   > Qt Version: 6.8.1
   > Kernel Version: 6.12.9-200.fc41.x86_64 (64-bit)
   > Graphics Platform: Wayland
   > Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
   > Memory: 30.4 GiB of RAM
   > Graphics Processor: AMD Radeon RX 5700
   > ~~~

ADDITIONAL INFORMATION
----------------------

This also applies to https://bugs.kde.org/show_bug.cgi?id=490953#c0, so perhaps a meta-issue should be created to track these, for it would demonstrate how many KCMs are non-compliant. I don't mind testing them and creating bugs for each, if so.

Comment 1 Roke Julian Lockhart Beedell 2025-01-22 19:15:39 UTC

(In reply to Roke Julian Lockhart Beedell from comment #0)  
Like https://bugs.kde.org/show_bug.cgi?id=490953#c1, perhaps I should have tested more - it also doesn't apply to the inactive device toggle, nor the "Volume Controls" page, so it's not limited to volume sliders.

Comment 2 Roke Julian Lockhart Beedell 2025-01-22 19:18:24 UTC

Created attachment 177601 [details]
The latest version of the report, because BZ doesn't support post edits.

Comment 3 Nate Graham 2025-01-22 22:08:00 UTC

AFAIK this is intentional since almost none of the controls here really have a default state. What would be a default volume level, for example? Would that concept really make any sense?

That's why there's no "Defaults" button to reset everything, either.

Comment 4 Roke Julian Lockhart Beedell 2025-01-22 22:15:09 UTC

(In reply to Nate Graham from comment #3)  

> AFAIK this is intentional since almost none of the controls here really have a default state. What would be a default volume level, for example? Would that concept really make any sense?

Yeah, it was a poor example to focus on.

I presume the others - the toggles and checkboxes in the linked page - still make sense, though? There are also even more things in that page that can be changed than I mentioned, like device names and stream-specific default devices. Those would definitely make sense to highlight.

> That's why there's no "Defaults" button to reset everything, either.

I've often wondered why they don't have a defaults option, too. I've accidentally set wrong values with my scroll-wheel in the past, completely screwing my sound card configuration.

Comment 5 Roke Julian Lockhart Beedell 2025-01-22 22:21:27 UTC

(In reply to Roke Julian Lockhart Beedell from comment #4)

> > That's why there's no "Defaults" button to reset everything, either.
> 
> I've often wondered why they don't have a defaults option, too. I've accidentally set wrong values with my scroll-wheel in the past, completely screwing my sound card configuration.

I've actually got a verifiable example of this: https://discuss.kde.org/t/scrolling-using-the-mouse-scroll-wheel-in-kcm-sound-changes-preferences/13124?u=rokejulianlockhart.

Comment 6 Nate Graham 2025-01-23 15:28:58 UTC

Yeah, on second thought it's reasonable to implement support for *some* settings that have a logical default value.