Arch Linux

This method still works if you have a key set to send XF86ClearGrab, which defaults to CTRL+ALT+Numpad_Multiply (or KPMU in xkbcomp parlance).

Essentially, the bug remains, but it's not in [xorg], but rather [xscreensaver] and other screen-locking programs, as it's up to an individual program to disable the behavior (and screen-locking apps are exactly what should be doing that).

can you be more specific in your case? What do you use etc

I take back what I said about xscreensaver. It might not even be a bug.

I will say, however, that sending the XF86ClearGrab will cause a screen locking program to quit. I am now uncertain whether it is possible for a program to disable that behavior, as there is some discussion on arch-general stating that a linked article is incorrect.

My case is simply that CTRL+ALT+KPMU sends XF85ClearGrab, and will kill xscreensaver (or alock) if it's doing its screen locking job. I made a custom keyboard layout with xkbcomp (and judicious application of vi), which is attached hereto. As pointed out on arch-general, this may indeed simply be a case of a keybinding that just shouldn't be there unless you are debugging full screen programs and are OK with the consequences.

If there was a way to retract my reopen request, I would have before you acted on it.

Heey! Is it going to be fixed? Just disable ClearGrab/Ungrab in /usr/share/X11/xkb/compat/xfree86, why not?

44,49c44,49
< interpret XF86_Ungrab {
< action = Private(type=0x86, data="Ungrab");
< };
< interpret XF86_ClearGrab {
< action = Private(type=0x86, data="ClsGrb");
< };
---
> // interpret XF86_Ungrab {
> // action = Private(type=0x86, data="Ungrab");
> // };
> // interpret XF86_ClearGrab {
> // action = Private(type=0x86, data="ClsGrb");
> // };

Really, it is a security hole while it is not fixed in a *lock programs, but a such simple workaround is good enough for the moment, IMHO...

Please, close this bug. Fixed in xkeyboard-config 2.4.1-3