Different behaviour than ALT+F1 on Plasma 2 (Fedora 22)

[bllngr]

While it's base functionality works in Plasma 2 on Fedora 22, I notice the following difference between pressing the Super key and pressing ALT+F1:

1. In Firefox, the Menu toolbar is shown (triggers on ALT press). This doesn't happen on ALT+F1.
2. Pressing Super a second time doesn't close Kickoff. Again, this works with ALT+F1.

Version info:

$ rpm -q plasma-workspace  libX11-devel libXtst-devel 
plasma-workspace-5.2.2-1.fc22.x86_64
libX11-devel-1.6.3-1.fc22.x86_64
libXtst-devel-1.2.2-4.fc22.x86_64

Debug output (pressed Super two times):

/ksuperkey -h
./ksuperkey: invalid option -- 'h'
Usage: ./ksuperkey [-d] [-t timeout_ms] [-e <mapping>]
Runs as a daemon unless -d flag is set
[test@yoga ksuperkey]$ ./ksuperkey -d
sig_handler running...
Intercepted key event 3, key code 36
Intercepted key event 2, key code 133
Key pressed!
Intercepted key event 3, key code 133
Key released!
Generating Alt_L!
Generating F1!
Ignoring generated event.
Ignoring generated event.
Ignoring generated event.
Ignoring generated event.
Intercepted key event 2, key code 133
Key pressed!
Intercepted key event 3, key code 133
Key released!
Generating Alt_L!
Generating F1!
Ignoring generated event.
Ignoring generated event.
Ignoring generated event.
Ignoring generated event.
Intercepted key event 4, key code 1
Intercepted key event 5, key code 1
Intercepted key event 2, key code 37
Intercepted key event 2, key code 54
^CCaught signal 2!
sig_handler exiting...
main exiting

I don't know if this used to work better before, it's the first time running ksuperkey. In any case, thanks for your work!

[hanschen]

Sorry about the late reply, and thanks for reporting these issues.

1. I can reproduce this issue, but unfortunately I don't how to fix it. You could try to report it to the xcape bug tracker and see if the original author has any ideas (also, I'm not sure if it's related to https://github.com/alols/xcape/issues/16 or not). A temporary workaround could be to bind "Show application launcher" to a different keybinding, e.g. Super_L + F1, and change the keys ksuperkey generates through the -e flag (see README.md).
2. I haven't switched to Plasma 5 yet so I can't test this, but I know it works fine in Plasma 1. I'll keep this report open until I'm able to test it and see where the issue lies, or until someone else creates a pull request, or it gets fixed in Kickoff.

[Zzooouhh]

I've found a workaround in Plasma 5 (OpenSUSE) by launching two instances of ksuperkey at once. Every once in a while the kickoff closes itself as soon as it opens upon pressing Super_L this way, but otherwise it's capable of both opening and closing it.

[LinuxUserpacmanapt]

I also had a problem with assigning the application launcher to ALT+F1 so worked better when I set it to ALT+F2. Using Garuda Dragonized KDE plasma 5.23.3

[hanschen]

Note that Plasma now includes a feature similar to ksuperkey by default (starting from Plasma 5.8), so there's no need to use ksuperkey unless you want some other mappings.

[LinuxUserpacmanapt]

I did not know that and I was looking into it but didn't find info on that.

[LinuxUserpacmanapt]

Okay found out my machine is using plasma version 5.23.3 and framework 5.88.0 so might not be on Garuda yet

[hanschen]

Okay found out my machine is using plasma version 5.23.3 and framework 5.88.0 so might not be on Garuda yet

Your version should have it by default then, Plasma 5.8 was released in 2016 I believe. According to a Reddit comment, Meta will call qdbus org.kde.plasmashell /PlasmaShell activateLauncherMenu, which is the first launcher widget you have with a global shortcut. So make sure your launcher has a global shortcut set. You can also try to run that command and see if anything happens.

Here's some more information (not sure if it's still up-to-date): https://zren.github.io/kde/#windowsmeta-key