Bug 355322

Summary: The keyboard shortcut to the Application Dashboard doesn't work after KDE startup
Product: [Unmaintained] kdeplasma-addons Reporter: Xavion <Xavion.0>
Component: Application DashboardAssignee: Eike Hein <hein>
Status: RESOLVED FIXED    
Severity: normal CC: mgraesslin, notuxius, plasma-bugs-null, stasnel, Xavion.0
Priority: NOR    
Version First Reported In: 5.4.3   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Xavion 2015-11-14 01:40:14 UTC 
Firstly, I'll provide some background information.  I log into KDE via the SDDM, and my Application Dashboard widget is located on the main panel.  Also, I have assigned the "Meta (Windows key) + a" keyboard shortcut to it.

I notice that, after logging in, said shortcut only works when my mouse cursor is hovering on the main panel.  If it's instead located elsewhere on the screen at the time, nothing happens when I press "Meta+a".  This is the case even if I try it multiple times.

However, after killing and relaunching "plasmashell", the shortcut works first time (every time).  So, as a workaround, I've instructed KDE to launch the following shell script on startup.  It adds some delay to the login process, so this bug still needs to be fixed.

`--> cat `which Restart-Plasma`
#!/bin/bash

killall plasmashell
plasmashell &>/dev/null &

Before doing this, I tried to get it going via XbindKeys (without success).  I added the following lines to my "~/.xbindkeysrc" file.  Unfortunately, "plasmashell" still needed to be killed before this would work.  BTW, can you give the D-Bus shortcut a better name than "activate widget 18"?

"qdbus org.kde.kglobalaccel /component/plasmashell org.kde.kglobalaccel.Component.invokeShortcut 'activate widget 18'"
Mod4 + a


Reproducible: Always
Comment 1 Eike Hein 2015-11-14 19:52:18 UTC 
Martin, any idea about this?
Comment 2 Martin Flöser 2015-11-15 10:30:15 UTC 
ah yeah, that sounds like the known bug that Qt doesn't forward keyboard mapping events, so kglobalaccel doesn't notice the changes. Wayland will fix it (as always).
Comment 3 Eike Hein 2015-11-16 13:43:26 UTC 
How should we resolve this ticket then?
Comment 4 Martin Flöser 2015-11-16 13:53:01 UTC 
well needs more investigation. Whether it is that problem, if it is, it should get duplicated with the corresponding bug in kglobalaccel.
Comment 5 Xavion 2015-11-16 19:39:19 UTC 
If you guys aren't able to reproduce this bug at your end, let me know if you'd like me to run more tests here.
Comment 6 Alexander Mentyu 2018-08-07 10:05:35 UTC 
Cannot reproduce, is this issue still relevant?

Distribution: KDE neon Developer Edition
Kernel: 4.15.0-29-generic
Plasma: 5.13.80
Apps: 18.11.70
Qt: 5.11.1
Frameworks: 5.48.0
Comment 7 Xavion 2018-08-07 21:43:40 UTC 
No, it seems to have been fixed.  I haven't seen it for a while.