Bug 315182

Summary: "save as default" menu can't be operated by keyboard, always saves
Product: [Applications] systemsettings Reporter: Christoph Lange <langec>
Component: kcm_randrAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: hbock
Priority: NOR    
Version: 4.10.0   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:

Description Christoph Lange 2013-02-15 08:02:43 UTC
In the RandR system settings panel I opened the "save as default" menu button using the keyboard (Alt+S) and then changed my mind, i.e. didn't want to save. This didn't work as expected. Resetting didn't work either.

Reproducible: Always

Steps to Reproduce:
1. In "Size & Orientation", open the "save as default" menu by keyboard shortcut. It's important that you open it using the underlined letter (should be Alt+S), not by hitting Space when it's focused.
2. Hit "Escape"
3. (From here onwards the steps are independent from steps 1 and 2!) – open "save as default" once more by keyboard shortcut
4. select "Reset" either by Alt+R or cursor keys plus Return.

Actual Results:  
Steps 1&2: "Configuration has been set as the desktop default".

Steps 3&4: first "Default desktop setup has been reset", then "Configuration has been set as the desktop default"

Expected Results:  
Steps 1&2: do nothing

Steps 3&4: reset

As this problem doesn't occur when the "save as default" menu is opened by other means than Alt+S, e.g. by Space or using the mouse (even if then you continue to operate it by keyboard!), it seems to me that the Alt+S shortcut is processed twice: Once for opening the menu, and then once more for selecting its entry "save as default".
Comment 1 David Edmundson 2015-01-22 12:08:01 UTC
Thanks for reporting your bug.

Since reporting Krandr has since been replaced by KScreen. It is available in the Plasma 4 series, and is default in Plasma 5 onwards.

I hope this solves your issue. If you still have a problem after upgrading please reopen a new bug under kscreen.

Thanks