On 2/13/06, Loïc Minier <[EMAIL PROTECTED]> wrote:
update: xev recognizes keys always, but desktop environment does not.
when metacity does not interpret the multimedia keys, xev reports like this:
KeyPress event, serial 29, synthetic NO, window 0x2e00001,
root 0x4c, subw 0x0, time 365327, (116,570), root:(1264,734),
state 0x0, keycode 133 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 29, synthetic NO, window 0x2e00001,
root 0x4c, subw 0x0, time 365510, (116,570), root:(1264,734),
state 0x0, keycode 133 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
and when metacity interprets xev reports the it lost focus and gained it again (FocusOut, PropertyNotify atom 0x12c _NET_WM_ICON_GEOMETRY, FocusIn, KeymapNotify ...), so it even did not get a chance to record the multimedia keys.
the interesting part is the volume up/down keys work, but not the play, next etc.
then I played with Desktop->Preferences->"Keyboard shortcuts".
after re-setting the non-functional keys xev started recognizing them as follows:
KeyPress event, serial 26, synthetic NO, window 0x3200001,
root 0x4c, subw 0x0, time 909140, (1364,642), root:(1374,714),
state 0x0, keycode 133 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 29, synthetic NO, window 0x3200001,
root 0x4c, subw 0x0, time 909316, (1364,642), root:(1374,714),
state 0x0, keycode 133 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES,
XLookupString gives 0 bytes:
(note that Keyboard shotcut panel recognizes play by 0x85 = 133 keycode)
Then I reconfigured Keyboard shortcuts again, this time 0x85 keycode got replaced with XF86AudioPlay which became consistent with xev and metacity/global_bindings registry, but still those keys were not interpreted.
Then I went to metacity/global_bindings registry and re-edited the run_command_1 and other keys with XF86AudioXyz strings and it started to work.
So this last workaround forces metacity to start recognizing stuff, another is to logout-login, as you can see this is far from usable.
I attach my .xsession-errors. There you'll see many messages about mounting usb disk, which seems to be normal except few assertions at the end, I did not notice them when media keys worked.
No, I did not. I could not reproduce this for now, though. It seems the xorg keys issue was temporary (probably after upgrade without restart or smth like that).
Hi,
On Mon, Feb 13, 2006, marius mikucionis wrote:
> Usually it works, but sometimes it doesn't, then I just logout and login
> again... but now Xorg (linux kernel?) stopped recognizing media keys
> completely, so I cannot verify now.
update: xev recognizes keys always, but desktop environment does not.
when metacity does not interpret the multimedia keys, xev reports like this:
KeyPress event, serial 29, synthetic NO, window 0x2e00001,
root 0x4c, subw 0x0, time 365327, (116,570), root:(1264,734),
state 0x0, keycode 133 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 29, synthetic NO, window 0x2e00001,
root 0x4c, subw 0x0, time 365510, (116,570), root:(1264,734),
state 0x0, keycode 133 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
and when metacity interprets xev reports the it lost focus and gained it again (FocusOut, PropertyNotify atom 0x12c _NET_WM_ICON_GEOMETRY, FocusIn, KeymapNotify ...), so it even did not get a chance to record the multimedia keys.
the interesting part is the volume up/down keys work, but not the play, next etc.
then I played with Desktop->Preferences->"Keyboard shortcuts".
after re-setting the non-functional keys xev started recognizing them as follows:
KeyPress event, serial 26, synthetic NO, window 0x3200001,
root 0x4c, subw 0x0, time 909140, (1364,642), root:(1374,714),
state 0x0, keycode 133 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 29, synthetic NO, window 0x3200001,
root 0x4c, subw 0x0, time 909316, (1364,642), root:(1374,714),
state 0x0, keycode 133 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES,
XLookupString gives 0 bytes:
(note that Keyboard shotcut panel recognizes play by 0x85 = 133 keycode)
Then I reconfigured Keyboard shortcuts again, this time 0x85 keycode got replaced with XF86AudioPlay which became consistent with xev and metacity/global_bindings registry, but still those keys were not interpreted.
Then I went to metacity/global_bindings registry and re-edited the run_command_1 and other keys with XF86AudioXyz strings and it started to work.
So this last workaround forces metacity to start recognizing stuff, another is to logout-login, as you can see this is far from usable.
Ok, do you get any warning in your .xsession-errors from metacity when
it doesn't work anymore?
I attach my .xsession-errors. There you'll see many messages about mounting usb disk, which seems to be normal except few assertions at the end, I did not notice them when media keys worked.
Did you file a bug concerning the "Xorg stopped recognizing media keys
completely" problem already? If yes, what's its bug id (so that I can
mark this metacity bug as blocked by this Xorg bug), if no, could you
please do so?
No, I did not. I could not reproduce this for now, though. It seems the xorg keys issue was temporary (probably after upgrade without restart or smth like that).
Bye,
--
Loïc Minier < [EMAIL PROTECTED]>
Current Earth status: NOT DESTROYED
xsession-errors
Description: Binary data
