Bug 341817 - Only two shortcuts can be configured in KCM
Summary: Only two shortcuts can be configured in KCM
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_keys (show other bugs)
Version: 5.3.90
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Kügler
URL:
Keywords:
: 341816 343178 413542 415113 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-12-12 17:59 UTC by crog
Modified: 2020-04-30 17:18 UTC (History)
13 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.19.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description crog 2014-12-12 17:59:51 UTC
When setting a new shortcut to lock the session (system settings -> shortcuts; ksmserver -> lock screen), the default shortcut (ctrl + alt + l) still functions in addition to the new setting.

In my particular example, setting it to Meta + L locks the screen as one would expect, but ctrl+alt+l also locks the screen. Another user has noted that setting the shortcut to None does not actually disable it.

Reproducible: Always

Steps to Reproduce:
1. Change the shortcut from the default to any other key combination
2. Use the new shortcut key combination (if applicable) to lock the session
3. Unlock the session
4. Use the default of ctrl+alt+l to attempt to lock the session again

Actual Results:  
Step 4 succeeds in locking the session.

Expected Results:  
Step 4 should noop.
Comment 1 Bhushan Shah 2014-12-16 12:04:00 UTC
I looked into this and I can confirm that, it looks like it is only overriding first shortcut here. (same problem for krunner)

Dec 16 17:31:02 archbox kglobalaccel5[486]: Unregistering key "Alt+Space" for "krunner" : "run command"
Dec 16 17:31:02 archbox kglobalaccel5[486]: Unregistering key "Alt+F2" for "krunner" : "run command"
Dec 16 17:31:02 archbox kglobalaccel5[486]: Unregistering key "Search" for "krunner" : "run command"
Dec 16 17:31:02 archbox kglobalaccel5[486]: Registering key "Alt+S" for "krunner" : "run command"
Dec 16 17:31:02 archbox kglobalaccel5[486]: Registering key "Alt+F2" for "krunner" : "run command"
Dec 16 17:31:02 archbox kglobalaccel5[486]: Registering key "Search" for "krunner" : "run command"
Comment 2 Bhushan Shah 2014-12-18 11:54:46 UTC
Git commit e94f325ec85fc9bfa27238c0109f4ad80d65db3f by Bhushan Shah.
Committed on 18/12/2014 at 11:44.
Pushed by bshah into branch 'master'.

Reorder the shortcuts

KGlobalAccel takes first shortcut in list as primary and other as
secondary shortcut, and KShortcutsDialog only allows to edit primary
shortcut, see bug https://bugs.kde.org/show_bug.cgi?id=341942

This result in problem where only Screensaver key is configurable and
Alt+Ctrl+L can not be removed. Someone will less likely use Screensaver
key for other purposes.

Reviewed-by: Marco Martin <notmart@gmail.com>

M  +1    -2    ksmserver/screenlocker/ksldapp.cpp

http://commits.kde.org/plasma-workspace/e94f325ec85fc9bfa27238c0109f4ad80d65db3f
Comment 3 Bhushan Shah 2015-02-02 17:01:55 UTC
*** Bug 341816 has been marked as a duplicate of this bug. ***
Comment 4 David Edmundson 2015-02-03 09:18:28 UTC
So this is fixed then?
Comment 5 Bhushan Shah 2015-02-03 16:51:46 UTC
Lock screen problem is fixed but potential problem in KGlobalAccel is not fixed, I will reopen this bug and assign it to kglobalaccel
Comment 6 Bhushan Shah 2015-02-03 17:01:35 UTC
Erm, sorry forgot to move to kglobalaccel.. sorry for noise
Comment 7 Bhushan Shah 2015-02-08 16:26:03 UTC
*** Bug 343178 has been marked as a duplicate of this bug. ***
Comment 8 Moritz Bunkus 2015-06-05 07:47:28 UTC
No, this is not fixed in Frameworks 5.3. I cannot get Alt+F2 to work in applications as It will always be used by krunner, even if I configure krunner's primary accelerator to something else. Highly annoying to me.
Comment 9 Nate Graham 2019-11-25 05:11:05 UTC
*** Bug 413542 has been marked as a duplicate of this bug. ***
Comment 10 Nate Graham 2019-12-13 11:04:05 UTC
*** Bug 415113 has been marked as a duplicate of this bug. ***
Comment 11 Andy Great 2020-02-15 19:37:50 UTC
I upgrade my openSUSE Tumbleweed which upgrade KDE from 5.17 to 5.18 and this same bug come back after doing the work around.

Operating System: openSUSE Tumbleweed 20200213
KDE Plasma Version: 5.18.0
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1
Kernel Version: 5.5.2-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz
Memory: 7.5 GiB of RAM
Comment 12 Andy Great 2020-02-15 19:55:20 UTC
The problem gone after reboot, maybe some random glitch.