Assigning Mod1+Space

[Martin Dietze]

After having returned to WM I have been observing a strange effect.

I have mapped "Run command" to Mod1+Space. In a fresh WM session this works just fine. Howevre at some point, I cannot determine which, that shortcut no longer works. I can reassign the action to something else, e.g. Ctrl-Shift-Space, and this works, however Mod1+Space does not.

I usually have Mod1+Space mapped to something like this in other desktop environments, too, like Plasma, Gnome, ... hence my intuition tells me that some background process started by something I don't know has started grabbing this shortcut. While... Mod1+Space simply does nothing, no "krunner" or whatever else appears, so this really remains a mystery.

Anybody got a hint? 

Cheers,

m.

[Martin Dietze]

Replying to myself: the culprit is kglobalaccel5 which is started as a user job by systemd.

In order to disable it only when in a WM session I have for now added an entry systemctl --user stop plasma-kglobalaccel to ~/GNUStep/Library/WindowMaker/autostart

Let's see how this works out.