On 03/05/2020 18:14, Andriy Gapon wrote:
> I think I found a problem, maybe someone will recognize a root cause behind
> it.
>
> I looked at .config/kglobalshortcutsrc and found some entries that looked
> weirdly different from the rest. Here they are:
> display=Display,Display\tMeta+P,Switch Display
> Lock Session=Meta+L,Meta+L\tCtrl+Alt+L\tScreensaver,Lock Session
> ExposeAll=Ctrl+F10,Ctrl+F10\tLaunch (C),Toggle Present Windows (All desktops)
[snip]
> Then, I started plasma and executed 'kquitapp5 kglobalaccel'. Then I edited
> the
> file again. And then started kglobalaccel5.
> This time my modifications stayed unchanged. At least, while the session is
> still running.
> And! Win+L now locked the screen, Win+D showed the desktop, Win+E launched
> Dolphin, etc!
Those \t entries were a red herring.
>From a cursory look through the code I see that \t is indeed a separator used
>by
kglobalaccel to multiple separate key combinations assigned to the same action
and type (default, custom). Not sure if the UI supports such multiple
combinations, but the backend certainly does.
Anyway, more importantly, simply restarting kglobalaccel ('kquitapp5
kglobalaccel ; kglobalaccel5 &') fixes the meta key shortcuts, no need to edit
kglobalshortcutsrc.
So, it must be something in startup code of some kde/plasma component that
messes up "Meta" key.
But what and how?..
--
Andriy Gapon
