Bug 326590

Summary: Audio settings take effect even if I don't click "Apply".
Product: [Frameworks and Libraries] Phonon Reporter: Dima Ryazanov <dima>
Component: settingsAssignee: Harald Sitter <sitter>
Status: CONFIRMED ---    
Severity: normal CC: andrew.crouthamel, bugs, myriam
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Dima Ryazanov 2013-10-25 02:32:26 UTC
In "Audio and Video Settings", in the "Audio Hardware Setup" tab, select a different "Profile". The change takes effect immediately, even if you don't click "Apply". Moreover, if you try to exit, you get a prompt about unsaved changes - and clicking "Discard" doesn't do anything.

Reproducible: Always
Comment 1 Graeme Hewson 2013-12-24 17:53:40 UTC
I confirm this in 4.12.0.

If you click the blue arrow to return to the Settings overview, there's a popup titled "Apply Settings - System Settings" with the text "The settings of the current module have changed. Do you want to apply the changes or discard them?" If you click Discard, then go back to the Audio Hardware Setup tab, you can see the new setting has been applied and not discarded.

Also, if you select another sound card, even without changing anything, the Apply button becomes ungreyed.

You might want to go to the device setup just to use the Speaker Placement and Testing function and not make any changes. At the moment you have to click Apply unnecessarily to quit.
Comment 2 Andrew Crouthamel 2018-11-11 04:33:59 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Graeme Hewson 2018-11-11 08:40:39 UTC
Bug is still present in System Settings 5.13.5.

I'm setting the status to Reported, even though I'm not the submitter of the bug.
Comment 4 Andrew Crouthamel 2018-11-12 03:15:31 UTC
Thanks for the update!