Keybindings consisting completely of modifier keys no longer work

[Max Bowsher]

Binary package hint: compiz

In Jaunty's compiz, keybindings that consist entirely of modifier keys no longer work. e.g. the "Water Effect" plugin's "Initiate" default keybinding is <Control><Super>. This doesn't work. Changing it to a keybinding including a non-modifier key makes it work. Changing other plugin's effects to keybindings that are entirely modifier keys reproduces the problem with them.

This is a regression from Intrepid.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
MachineType: Supermicro P8SAA
NonfreeKernelModules: nvidia
Package: compiz 1:0.8.2-0ubuntu7
PackageArchitecture: all
ProcCmdLine: root=LABEL=epsilon ro ht=on crashkernel=384M-2G:64M@16M,2G-:128M@16M
ProcEnviron:
 LC_COLLATE=C
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.40-generic
SourcePackage: compiz

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82925X/XE Memory Controller Hub [8086:2584] (rev 05)
     Subsystem: Super Micro Computer Inc Device [15d9:6480]
01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 6500 [10de:0160] (rev a1)
     Subsystem: XFX Pine Group Inc. Device [1682:2153]

[Steve Beattie (sbeattie)]

Confirming behavior on jaunty, not sure if this is an issue with compiz itself or the settings manager.

[Ken VanDine (ken-vandine)]

Upstream bug report: http://bugs.opencompositing.org/show_bug.cgi?id=1155

[Ken VanDine (ken-vandine)]

Upstream compiz things this is actually a bug related to xkb in libX11. Below is an excerpt from the compiz bug report:

Ok, looks like Jaunty's libX11 and/or X server are broken wrt Xkb events.
/usr/include/X11/XKBlib.h defines XkbStateNotifyEvent, which has a event_type
member:
http://cgit.freedesktop.org/xorg/lib/libX11/tree/include/X11/XKBlib.h#n116

The comment in the header file says that this member is either set to KeyPress
or KeyRelease, which are defined to 2 and 3 according to the X protocol
headers:
http://cgit.freedesktop.org/xorg/proto/xproto/tree/X.h#n186

For me, this was the case:
triggering state notify bindings in plugin text, mods 4, type 2
triggering state notify bindings in plugin workarounds, mods 4, type 2

For you, it's not:
> triggering state notify bindings in plugin wobbly, mods 4, type 78
> triggering state notify bindings in plugin switcher, mods 4, type 78

I am not sure where the values 78 and 79 are coming from, as they are defined
nowhere in Jaunty's X11 headers. But that's definitely the direction I would
suggest to look at :)

BTW, bindings with normal (non-modifier) keys are not affected, because they
are handled differently (not via XkbStateNotifyEvent, but via KeyPressEvent).

[Max Bowsher (maxb)]

Seems to be fixed in Karmic.

[COLIN Stéphane (bigbob-fun)]

Hi all,

I have made mistake when changing status to 'Fix Released' (2 times).

So, now I don't know anymore what is the real status of this bug ...

I have backported many packages from karmic to my jaunty, but actually, I'm in the step where <ctrl>+<super> sequence doesn't work.

Anyone know exactly if it was fixed somewhere, and if so what is the package I need to backport on my side to be able to use the sequence ?

A++

[COLIN Stéphane (bigbob-fun)]

Ok,

As of now, I'm running Karmic.

All I can say, the bug is not fixed at all ...

Someone can help on this problem please ?*

I can check to backport package from lucid for testing if it was fixed, but I don't know what package to backport to check it ...

A++