Bug 430710

Summary: Defining key shortcuts has stopped working
Product: [Applications] systemsettings Reporter: geisserml <geisserml>
Component: kcm_khotkeysAssignee: Michael Jansen <kde>
Severity: normal CC: andihartmann, bugseforuns, geisserml, panchopapada, plasma-bugs
Priority: NOR    
Version: 5.20.4   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: button text does not change and keys won't get recognised

Description geisserml 2020-12-22 14:05:32 UTC
Created attachment 134267 [details]
button text does not change and keys won't get recognised

I am completely unable to define any custom key shortcuts. When I click on the button "None" to define a new shortcut, nothing happens and the keys I press are not getting recognised. Normally, the text should change from "None" to "Input..." when I click the button, but even this does not happen.

1. konsole > systemsettings5 khotkeys
2. go to any of your custom actions
3. switch to second tab "trigger"
4. press the button Shortcut: "None"
-> the text will not change to "Input..." as it should
-> the keys you press will not get recognised

This bug was (I believe) introduced with the latest KDE Applications update 5.20.4 which caused most of my existing shortcuts to get lost, and now I'm unable to redefine them.
I of course can't know whether this bug is generally reproducable, or whether some specific preconditions are required to make this happen, but I don't think I have any unusual configuration...

Beyond this issue I think the way how defining custom shortcuts in KDE works would need an overall revision.

Operating System: KDE neon 5.20
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-58-generic
Comment 1 Andreas Hartmann 2020-12-22 19:40:25 UTC
Exactly same problem here. Should really be fixed ASAP.
Comment 2 geisserml 2020-12-22 20:31:36 UTC
@ Andreas Hartmann: I agree it's little annoying, but we should be patient and let the devs have their winter holidays ;) They're all contributing voluntarily and probably have lots of important personal stuff to care about, especially in these times.
Comment 3 geisserml 2020-12-22 20:35:27 UTC
*it's a little*
Comment 4 geisserml 2020-12-22 21:06:25 UTC
I know almost nothing about C++/Qt, but my best guesses are that the problem is somwhere around khotkeys/kcm_hotkeys/triggers/shortcut_trigger_widget.cpp ...
Comment 5 geisserml 2020-12-22 21:20:43 UTC
I am wondering which commit has introduced the bug, because it worked correctly before the latest updates...
Perhaps one of the changes made by @sandsmark about 6 months ago, but that's almost too long ago
Comment 6 geisserml 2020-12-22 21:29:39 UTC
I'm probably wrong, but this commit (https://invent.kde.org/plasma/khotkeys/-/commit/f42a8446be7657ec3397be7fc253f7f64cb31392) seems a bit suspicious to me
Comment 7 José 2020-12-23 12:46:41 UTC
I confirm. It happens in KDE Neon in a fresh/updated installation
Comment 8 Patrick Silva 2020-12-23 18:54:29 UTC

*** This bug has been marked as a duplicate of bug 430388 ***
Comment 9 Andreas Hartmann 2020-12-24 07:08:44 UTC
The fix mentioned here https://bugs.kde.org/show_bug.cgi?id=430388 works for me. Thanks!