Bug 409129

Summary: Shortcuts stop working after switching virtual console
Product: [Applications] systemsettings Reporter: Nagy Tamás <tbondvagyok>
Component: kcm_khotkeysAssignee: Michael Jansen <kde>
Status: RESOLVED FIXED    
Severity: minor CC: bugseforuns, smirky, tbondvagyok
Priority: NOR    
Version First Reported In: 5.20.3   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Nagy Tamás 2019-06-24 12:48:27 UTC 
SUMMARY
Custom shortcuts doesn't work after switching to a vconsole and back. (Global and Standard shortcuts still work)

STEPS TO REPRODUCE
1. Set a custom shortcut in kmenuedit or in System settings > Shortcuts > Custom shortcuts (for example Ctrl+Shift+Esc to KSysGuard)
2. Check that the shortcut works.
3. Switch to another tty.
4. Switch back to the previous tty.
5. Check that the shortcut doesn't work any more. (But shortcuts like Meta+D still works)

OBSERVED RESULT
The set shortcut didn't do anything after switched virtual consols.

EXPECTED RESULT
The shortcuts work after the virtual console switch.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.15.1
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.4

ADDITIONAL INFORMATION
I noticed that after some time (or for some event) KDE reinitializes khotkeys. I checked the journalctl and saw that it runs the following command: `/usr/bin/kcmshell5 khotkeys` If I switch ttys and run this command, shortcuts starts to work again immediately. But it disconnect my bluetooth connections, and pops up the network interface connected notification also starts the Custom Shortcuts settings application. I think it reloads all module, which is very fustrating.
Comment 1 Patrick Silva 2020-02-12 15:23:35 UTC 
cannot reproduce here.

Operating System: Arch Linux 
KDE Plasma Version: 5.18.0
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1
Comment 2 Bogomil Vasilev 2020-08-10 09:28:28 UTC 
Perhaps my ticket refers to the same issue but reproducing it in another way:
https://bugs.kde.org/show_bug.cgi?id=425082
Comment 3 Nagy Tamás 2021-06-21 09:28:18 UTC 
I don't know when it happened, but it seems to be solved.