Bug 438534 - System Settings automatically discards unapplied changes in screenlocker KCM if the 'home' button is pressed.
Summary: System Settings automatically discards unapplied changes in screenlocker KCM ...
Status: RESOLVED DUPLICATE of bug 419592
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_screenlocker (show other bugs)
Version: 5.22.0
Platform: Other Other
: HI normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-13 06:55 UTC by Kishore Gopalakrishnan
Modified: 2021-06-13 13:34 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kishore Gopalakrishnan 2021-06-13 06:55:02 UTC
SUMMARY
If we click the 'home' button (in the sidebar) to leave the screenlocker KCM, System Settings seems to forget any unapplied changes made by the user (and does not ask whether to apply/discard).

STEPS TO REPRODUCE
1. Go to 'System settings > Workspace Behaviour > Screen locking'
2. Change any setting (but do not click 'apply')
4. Click 'back' (in the sidebar)
5. Click the 'home' button (in the sidebar)
6. Exit (close the window)

OBSERVED RESULTS
The user is never asked whether to apply/discard changes; the unapplied changes are automatically discarded.

EXPECTED RESULTS
System Settings should ask the user whether to apply/discard changed settings. This can happen while exiting the relevant KCM, which is already the behaviour exhibited by, for example, kcm_workspace.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.22.0
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 David Edmundson 2021-06-13 11:44:57 UTC
Confirmed. 

It appears to be anything in a multi-layer category when going to home doesn't unload properly.

There's a related bug that after clicking home and clicking workspace behaviour "screen locking" is selected but it isn't the tab shown.
Comment 2 Patrick Silva 2021-06-13 13:34:48 UTC
*** This bug has been marked as a duplicate of bug 419592 ***