https://bugzilla.novell.com/show_bug.cgi?id=756563 https://bugzilla.novell.com/show_bug.cgi?id=756563#c1 --- Comment #1 from Gary Ching-Pang Lin 2012-04-11 08:44:16 UTC --- (In reply to comment #0)

System: openSUSE:Factory + GNOME:Factory

After updating to gnome 3.4, all media keys, e.g. VolumeUp, BrightnessUp, Sleep, etc., didn't work any more. Xev caught the keycodes, so I attached gdb to gnome-settings-daemon and found the callback of the event filter was never called when I pressed the media keys. It seems the events were not passed from the root window to g-s-d for some reason.

To be more precise, the function, filter_key_events, did get some events from the root window, but none of them was a key event. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=756563 https://bugzilla.novell.com/show_bug.cgi?id=756563#c3 --- Comment #3 from Gary Ching-Pang Lin 2012-04-12 10:22:52 UTC --- I'm now pretty sure it's related to this g-s-d commit: common: Use XInput2 to capture and match keys http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=beafbd4b188d6cf... The other program, gsd-locate-pointer, which still uses XGrabKey is not effected, and the test program from 3.2.1 works in gnome 3.4. So we at least need an update for XInput2. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=756563 https://bugzilla.novell.com/show_bug.cgi?id=756563#c5 Vincent Untz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #5 from Vincent Untz 2012-05-11 11:33:04 UTC --- We have the new Xorg in Factory. And it's working! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.