Hello,
On an ordinary keyboard, the extended function keys, F13 to F24, should
be accessible as Shift + Fn, where Fn are the keys F1 to F12.
Well, up until a few days ago, the Shift+Fn combination was working as it
should. Then suddenly, Shift+Fn stopped working correctly. I noticed
it when using the Midnight Commander (MC) file manager where I extensively
use Shift+F5 and Shift+F6 to conveniently rename and copy files.
MC is a terminal program but the problem also shows up in some X programs
that use Shift+Fn combinations.
Because I have no need to closely monitor changes on my system I can't
actually pinpoint any new install that may be responsible. My first
guess would be a new version of xorg-server-1.11.1 that was emerged
on October 2.
I need to know how I can debug this situation further. Using xev
to record key presses gives the following output when using
Shift+F1:
KeyPress event, serial 40, synthetic NO, window 0xe00001,
root 0x121, subw 0x0, time 6919279, (23,152), root:(463,411),
state 0x0, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 40, synthetic NO, window 0xe00001,
root 0x121, subw 0x0, time 6921351, (23,152), root:(463,411),
state 0x1, keycode 67 (keysym 0xffffff, VoidSymbol), same_screen YES,
XKeysymToKeycode returns keycode: 63
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
The data for the F1 keypress is not correct. Compare this output with
the expected output that is shown in this forum thread:
http://forums.gentoo.org/viewtopic-t-524537-start-0.html
It appears that the X server is at fault.
Can anyone using xorg-server-1.11.1 very that the Shift+Fn keys
are broken?
Frank Peters
On an ordinary keyboard, the extended function keys, F13 to F24, should
be accessible as Shift + Fn, where Fn are the keys F1 to F12.
Well, up until a few days ago, the Shift+Fn combination was working as it
should. Then suddenly, Shift+Fn stopped working correctly. I noticed
it when using the Midnight Commander (MC) file manager where I extensively
use Shift+F5 and Shift+F6 to conveniently rename and copy files.
MC is a terminal program but the problem also shows up in some X programs
that use Shift+Fn combinations.
Because I have no need to closely monitor changes on my system I can't
actually pinpoint any new install that may be responsible. My first
guess would be a new version of xorg-server-1.11.1 that was emerged
on October 2.
I need to know how I can debug this situation further. Using xev
to record key presses gives the following output when using
Shift+F1:
KeyPress event, serial 40, synthetic NO, window 0xe00001,
root 0x121, subw 0x0, time 6919279, (23,152), root:(463,411),
state 0x0, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 40, synthetic NO, window 0xe00001,
root 0x121, subw 0x0, time 6921351, (23,152), root:(463,411),
state 0x1, keycode 67 (keysym 0xffffff, VoidSymbol), same_screen YES,
XKeysymToKeycode returns keycode: 63
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
The data for the F1 keypress is not correct. Compare this output with
the expected output that is shown in this forum thread:
http://forums.gentoo.org/viewtopic-t-524537-start-0.html
It appears that the X server is at fault.
Can anyone using xorg-server-1.11.1 very that the Shift+Fn keys
are broken?
Frank Peters