Bug#594089: keyboard-configuration: caps lock keycode problem

2010-10-27 Thread Tom Vier

On 10/27/2010 12:08 PM, Dmitry Torokhov wrote:
 On Wed, Oct 27, 2010 at 05:22:42PM +0200, Samuel Thibault wrote:
 Dmitry Torokhov, le Wed 27 Oct 2010 08:06:26 -0700, a écrit :
 Sure, but dumpkeys shows the table from scancodes to keycodes, not from
 input events to scancodes.

 I am just wondering if some of the translation is leaking even though
 the keyboard is in raw mode...

 OK, scratch that... Are there any other input devices? Anything
 connected via uinput and listening? What does /proc/bus/input/devices
 show? Maybe if Tom could compile and load evbug module it would show us
 where the additional events are coming form, becaus ethey surely are not
 generated by the keyboard itself (otherwise we'd have seen them in
 evtest output for that device).

Minor correction to what I wrote earlier about the scroll wheel. That is 
actually my mouse. It says Dell but it's really made by Logitech.


I just tried the console and what's funny is Favorites actually works as 
Capslock and Previous works as right-shift. X has the opposite problem.


In case anyone missed it, Debian Stable works fine with this keyboard. 
The keyboard on the working Stable machine is exactly the same (same usb 
id's). I'm not familiar with the input stack, but in case it is a kernel 
problem, the difference is:


Stable dist, working:
Linux zero 2.6.26-2-amd64 #1 SMP Thu Sep 16 15:56:38 UTC 2010 x86_64 
GNU/Linux


Testing dist, not working:
Linux tom 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 
GNU/Linux



/proc/bus/input/devices on the problem machine:

I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name=Macintosh mouse button emulation
P: Phys=
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=mouse0 event0
B: EV=7
B: KEY=7 0 0 0 0
B: REL=3

I: Bus=0003 Vendor=046d Product=c016 Version=0110
N: Name=Logitech Optical USB Mouse
P: Phys=usb-:00:13.0-1/input0
S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-1/5-1:1.0/input/input1
U: Uniq=
H: Handlers=mouse1 event1
B: EV=17
B: KEY=7 0 0 0 0
B: REL=103
B: MSC=10

I: Bus=0019 Vendor= Product=0001 Version=
N: Name=Power Button
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4
U: Uniq=
H: Handlers=kbd event4
B: EV=3
B: KEY=10 0

I: Bus=0019 Vendor= Product=0001 Version=
N: Name=Power Button
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
U: Uniq=
H: Handlers=kbd event5
B: EV=3
B: KEY=10 0

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name=PC Speaker
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input6
U: Uniq=
H: Handlers=kbd event6
B: EV=40001
B: SND=6

I: Bus=0003 Vendor=046d Product=c30a Version=0110
N: Name=Logitech Logitech USB Keyboard
P: Phys=usb-:00:13.0-2/input0
S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.0/input/input9
U: Uniq=
H: Handlers=kbd event2
B: EV=120013
B: KEY=10007 ff8007ff febeffdfffef fffe
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=046d Product=c30a Version=0110
N: Name=Logitech Logitech USB Keyboard
P: Phys=usb-:00:13.0-2/input1
S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.1/input/input10
U: Uniq=
H: Handlers=kbd mouse2 event3
B: EV=17
B: KEY=f f840334 60d8fafd01d008 1f 0
B: REL=103
B: MSC=10


--
Tom Vier t...@triadsys.com
Senior Net/Sys Admin
Triad Systems Engineering, Inc.




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cc870bb.2050...@triadsys.com



Bug#594089: keyboard-configuration: caps lock keycode problem

2010-10-26 Thread Tom Vier

On 10/25/2010 02:03 PM, Samuel Thibault wrote:
 Tom Vier, le Mon 25 Oct 2010 09:37:26 -0400, a écrit :
 On 10/25/2010 12:50 AM, Dmitry Torokhov wrote:
 On Sun, Oct 24, 2010 at 04:41:51PM +0200, Samuel Thibault wrote:
 The short story is: Tom's keyboard sends all that when he presses caps
 lock:

 press: 0x3a 0xe0 0x66
 repeat: 0x3a
 release: 0xba 0xe0 0xe6

 0xe0 0x66 happens to be the favorites key on his keyboard with
 internet navigation keys.  I thus believe there's a bug in his 
keyboard

 that needs to be filtered at the kernel level.

 The long story can be read on
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594089

 Hmm, the question is whether the real favorites key send the same
 usage and the fake one after caps lock. Any chance Tom could locate
 evtest utility and see what MSC_SCAN events being emitted?

 Sure. Here's caps-lock:

 Event: time 1288013671.633008, -- Report Sync 
 Event: time 1288013674.171812, type 4 (Misc), code 4 (ScanCode), 
value 70039

 Event: time 1288013674.171853, type 1 (Key), code 58 (CapsLock), value 1
 Event: time 1288013674.171862, -- Report Sync 
 Event: time 1288013674.172210, type 17 (LED), code 1 (CapsLock), value 1
 Event: time 1288013674.299553, type 4 (Misc), code 4 (ScanCode), 
value 70039

 Event: time 1288013674.299580, type 1 (Key), code 58 (CapsLock), value 0
 Event: time 1288013674.299593, -- Report Sync 


 Right-shift (the other problem key):

 Event: time 1288013798.388025, -- Report Sync 
 Event: time 1288013800.742088, type 4 (Misc), code 4 (ScanCode), 
value 700e5
 Event: time 1288013800.742130, type 1 (Key), code 54 (RightShift), 
value 1

 Event: time 1288013800.742142, -- Report Sync 
 Event: time 1288013800.861777, type 4 (Misc), code 4 (ScanCode), 
value 700e5
 Event: time 1288013800.861812, type 1 (Key), code 54 (RightShift), 
value 0

 Event: time 1288013800.861824, -- Report Sync 

 Could you also post results when pressing the favorite and the prev
 internet keys of your keyboard?

 Samuel


It's returning the same codes. Maybe what's going on here is that they 
never worked back in Stable and someone tried to fix those keys, not 
realizing they're the same codes as capslock and right-shift. I'll have 
to test it on my Stable machine tonight to see if those keys work or 
not, tho.


Favorites:
Event: time 1288041423.048839, -- Report Sync 
Event: time 1288041425.068704, type 4 (Misc), code 4 (ScanCode), value 70039
Event: time 1288041425.068742, type 1 (Key), code 58 (CapsLock), value 1
Event: time 1288041425.068754, -- Report Sync 
Event: time 1288041425.069105, type 17 (LED), code 1 (CapsLock), value 1
Event: time 1288041425.260313, type 4 (Misc), code 4 (ScanCode), value 70039
Event: time 1288041425.260343, type 1 (Key), code 58 (CapsLock), value 0
Event: time 1288041425.260347, -- Report Sync 

Previous:
Event: time 1288041443.531447, -- Report Sync 
Event: time 1288041445.318877, type 4 (Misc), code 4 (ScanCode), value 700e5
Event: time 1288041445.318915, type 1 (Key), code 54 (RightShift), value 1
Event: time 1288041445.318932, -- Report Sync 
Event: time 1288041445.438567, type 4 (Misc), code 4 (ScanCode), value 700e5
Event: time 1288041445.438606, type 1 (Key), code 54 (RightShift), value 0
Event: time 1288041445.438629, -- Report Sync 


--
Tom Vier t...@triadsys.com
Senior Net/Sys Admin
Triad Systems Engineering, Inc.




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cc6e9d8.8010...@triadsys.com



Bug#594089: keyboard-configuration: caps lock keycode problem

2010-10-26 Thread Tom Vier

On 10/25/2010 02:25 PM, Dmitry Torokhov wrote:

On Mon, Oct 25, 2010 at 08:03:20PM +0200, Samuel Thibault wrote:

Could you also post results when pressing the favorite and the prev
internet keys of your keyboard?



Actually, if these are all the events that evtest reports when pressing
CapsLock then I am confused where the favorites ghost press is coming
from... They are not emitted by the device. Do you have a funky keymap
loaded somewhere? Also, was 'showkey -s' issued while in X or in the
text console?


Console. I just ran it now and caps-lock has the same codes as 
favorites and right-shift has the same as previous. So it's not an X 
problem.


--
Tom Vier t...@triadsys.com
Senior Net/Sys Admin
Triad Systems Engineering, Inc.



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cc6eab5.9020...@triadsys.com



Bug#594089: keyboard-configuration: caps lock keycode problem

2010-10-26 Thread Tom Vier
 Descriptors:
   ** UNAVAILABLE **
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0004  1x 4 bytes
bInterval  10


--
Tom Vier t...@triadsys.com
Senior Net/Sys Admin
Triad Systems Engineering, Inc.



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cc7426c.8040...@triadsys.com



Bug#594089: keyboard-configuration: caps lock keycode problem

2010-10-25 Thread Tom Vier

On 10/25/2010 12:50 AM, Dmitry Torokhov wrote:

On Sun, Oct 24, 2010 at 04:41:51PM +0200, Samuel Thibault wrote:

The short story is: Tom's keyboard sends all that when he presses caps
lock:

press: 0x3a 0xe0 0x66
repeat: 0x3a
release: 0xba 0xe0 0xe6

0xe0 0x66 happens to be the favorites key on his keyboard with
internet navigation keys.  I thus believe there's a bug in his keyboard
that needs to be filtered at the kernel level.

The long story can be read on 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594089


Hmm, the question is whether the real favorites key send the same
usage and the fake one after caps lock. Any chance Tom could locate
evtest utility and see what MSC_SCAN events being emitted?

Thanks.


Sure. Here's caps-lock:

Event: time 1288013671.633008, -- Report Sync 
Event: time 1288013674.171812, type 4 (Misc), code 4 (ScanCode), value 70039
Event: time 1288013674.171853, type 1 (Key), code 58 (CapsLock), value 1
Event: time 1288013674.171862, -- Report Sync 
Event: time 1288013674.172210, type 17 (LED), code 1 (CapsLock), value 1
Event: time 1288013674.299553, type 4 (Misc), code 4 (ScanCode), value 70039
Event: time 1288013674.299580, type 1 (Key), code 58 (CapsLock), value 0
Event: time 1288013674.299593, -- Report Sync 


Right-shift (the other problem key):

Event: time 1288013798.388025, -- Report Sync 
Event: time 1288013800.742088, type 4 (Misc), code 4 (ScanCode), value 700e5
Event: time 1288013800.742130, type 1 (Key), code 54 (RightShift), value 1
Event: time 1288013800.742142, -- Report Sync 
Event: time 1288013800.861777, type 4 (Misc), code 4 (ScanCode), value 700e5
Event: time 1288013800.861812, type 1 (Key), code 54 (RightShift), value 0
Event: time 1288013800.861824, -- Report Sync 

--
Tom Vier t...@triadsys.com
Senior Net/Sys Admin
Triad Systems Engineering, Inc.



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cc58816.3090...@triadsys.com



Bug#594089: keyboard-configuration: caps lock keycode problem

2010-09-13 Thread Tom Vier



--
Tom Vier t...@triadsys.com
Senior Net/Sys Admin
Triad Systems Engineering, Inc.

703-956-1535 office
703-984-9093 cell
703-404-0308 helpdesk

On 09/07/2010 12:32 PM, Tom Vier wrote:

On 09/03/2010 07:55 PM, Samuel Thibault wrote:

Tom, le Mon 23 Aug 2010 11:43:53 -0400, a écrit :

The model name is logimel, which is set in both /etc/default/keyboard
and
/etc/X11/xorg.conf.


Which explains why Xorg has the behavior you describe: the logimel model
includes the logitech base, which includes the common navigation keys,
which makes XF86Back from 0xe0 0x6a, and XF86Favorites from 0xe0 0x66.

Do you actually have navigation keys on your keyboard? I'm afraid we'll
just have to blacklist it in the usb driver according to the usb ID.

Samuel


I have bunch of extra keys. 8) It's one of those internet keyboards
with keys for: email sms webcam itouch search shipping home favorites,
plus volume, track skip, play/pause, record.


Here's xev from Stable. It looks like in Testing that some of the extra 
key codes that show up in showkey are getting interpreted as additional 
key presses in Testing's xorg but not Stable's.


caps lock, then right shift

KeyPress event, serial 33, synthetic NO, window 0x2a1,
root 0x1ae, subw 0x0, time 9213660, (161,-9), root:(337,884),
state 0x12, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

PropertyNotify event, serial 33, synthetic NO, window 0x2a1,
atom 0x11c (XKLAVIER_STATE), time 9213663, state PropertyNewValue

KeyRelease event, serial 33, synthetic NO, window 0x2a1,
root 0x1ae, subw 0x0, time 9213780, (161,-9), root:(337,884),
state 0x12, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 33, synthetic NO, window 0x2a1,
root 0x1ae, subw 0x0, time 9217955, (161,-9), root:(337,884),
state 0x10, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

PropertyNotify event, serial 33, synthetic NO, window 0x2a1,
atom 0x11c (XKLAVIER_STATE), time 9217958, state PropertyNewValue

KeyRelease event, serial 33, synthetic NO, window 0x2a1,
root 0x1ae, subw 0x0, time 9218091, (161,-9), root:(337,884),
state 0x12, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 33, synthetic NO, window 0x2a1,
root 0x1ae, subw 0x0, time 9220699, (161,-9), root:(337,884),
state 0x12, keycode 36 (keysym 0xff0d, Return), same_screen YES,
   XLookupString gives 1 bytes: (0d) 
   XmbLookupString gives 1 bytes: (0d) 
XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x2a1,
root 0x1ae, subw 0x0, time 9220835, (161,-9), root:(337,884),
state 0x12, keycode 36 (keysym 0xff0d, Return), same_screen YES,
   XLookupString gives 1 bytes: (0d) 
XFilterEvent returns: False






--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c8e6861.1070...@triadsys.com



Bug#594089: keyboard-configuration: caps lock keycode problem

2010-09-07 Thread Tom Vier





On 09/03/2010 07:45 PM, Samuel Thibault wrote:

Tom Vier, le Fri 03 Sep 2010 16:35:47 -0400, a écrit :

On 09/02/2010 03:46 PM, Samuel Thibault wrote:

Hello,

Tom Vier, le Thu 02 Sep 2010 15:11:49 -0400, a écrit :

It says UNICODE mode and the codes for caps lock are:

press: 0x3a 0xe0 0x66
repeat: 0x3a
release: 0xba 0xe0 0x


0xe6 I guess?


Yes.


I also just discovered the right shift key goes back a page in
iceweasel. Here are the right-shift codes:

showkey -s:
press: 0x36 0xe0 0x6a
repeat: 0x36
release: 0xb6 0xe0 0xea


All this looks like one of the few keyboard glitches that linux-2.6
fixes for some keyboards known to be bogus, while other keyboards do use
these scancodes to report e.g. multimedia keys.  Could you try
showkey -s with the older, working kernel?


Stable (2.6.26) which worked fine gives the same as Testing (2.6.32):


When you say Stable, you mean both kernel and Xorg?  Could you also
run xev on your stable box?


I mean the debian stable release. I'll try it on my home machine, which 
has the same logitech keyboard.



press: 0x3a 0xe0 0x66
repeat: 0x3a
release: 0xba 0xe0 0xe6

...which makes me think it's an xorg problem, but I'm not familiar with
how the whole keyboard stack works.


It's a big mess :)


I wonder why the logitech generates so many codes.


It looks to me like a keyboard bug.  Do you see any pattern, e.g. does
the left shift key produce one too?  Do the keys which do produce extra
scancodes form any particular shape on the keyboard?


The only problem keys are caps-lock and right-shift, both upon key press.


Such bug should probably be fixed in the kernel, just like it is already
in atkbd.c for some keyboards.

Samuel


Showkey looks almost identical between kernels tho. I'll check my 
machine at home and see what xev shows.


--
Tom Vier t...@triadsys.com
Senior Net/Sys Admin
Triad Systems Engineering, Inc.

703-956-1535 office
703-984-9093 cell
703-404-0308 helpdesk




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c866828.7040...@triadsys.com



Bug#594089: keyboard-configuration: caps lock keycode problem

2010-09-07 Thread Tom Vier

On 09/03/2010 07:55 PM, Samuel Thibault wrote:

Tom, le Mon 23 Aug 2010 11:43:53 -0400, a écrit :

The model name is logimel, which is set in both /etc/default/keyboard and
/etc/X11/xorg.conf.


Which explains why Xorg has the behavior you describe: the logimel model
includes the logitech base, which includes the common navigation keys,
which makes XF86Back from 0xe0 0x6a, and XF86Favorites from 0xe0 0x66.

Do you actually have navigation keys on your keyboard?  I'm afraid we'll
just have to blacklist it in the usb driver according to the usb ID.

Samuel


I have bunch of extra keys. 8) It's one of those internet keyboards 
with keys for: email sms webcam itouch search shipping home favorites, 
plus volume, track skip, play/pause, record.


--
Tom Vier t...@triadsys.com
Senior Net/Sys Admin
Triad Systems Engineering, Inc.




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c866913.3030...@triadsys.com



Bug#594089: keyboard-configuration: caps lock keycode problem

2010-09-03 Thread Tom Vier

On 09/02/2010 03:46 PM, Samuel Thibault wrote:

Hello,

Tom Vier, le Thu 02 Sep 2010 15:11:49 -0400, a écrit :

It says UNICODE mode and the codes for caps lock are:

press: 0x3a 0xe0 0x66
repeat: 0x3a
release: 0xba 0xe0 0x


0xe6 I guess?


Yes.


I also just discovered the right shift key goes back a page in
iceweasel. Here are the right-shift codes:

showkey -s:
press: 0x36 0xe0 0x6a
repeat: 0x36
release: 0xb6 0xe0 0xea


All this looks like one of the few keyboard glitches that linux-2.6
fixes for some keyboards known to be bogus, while other keyboards do use
these scancodes to report e.g. multimedia keys.  Could you try
showkey -s with the older, working kernel?

Samuel


Stable (2.6.26) which worked fine gives the same as Testing (2.6.32):
press: 0x3a 0xe0 0x66
repeat: 0x3a
release: 0xba 0xe0 0xe6

...which makes me think it's an xorg problem, but I'm not familiar with 
how the whole keyboard stack works.



I tried a different usb keyboard (a Dell) under Testing and it works 
normally with iceweasel:

press: 0x3a
repeat: 0x3a
release: 0x3b

I wonder why the logitech generates so many codes.

--
Tom Vier t...@triadsys.com
Senior Net/Sys Admin
Triad Systems Engineering, Inc.

703-956-1535 office
703-984-9093 cell
703-404-0308 helpdesk




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c815c23.2070...@triadsys.com



Bug#594089: keyboard-configuration: caps lock keycode problem

2010-09-02 Thread Tom Vier

On 08/23/2010 11:59 AM, Samuel Thibault wrote:

forcemerge 594089 593742
reassign 594089 linux-2.6
retitle 594089 caps lock keyboard code problem
thanks

Hello,

Please do not submit another report for the same issue, just reassign.


Sorry, didn't know I could.


Tom, le Mon 23 Aug 2010 11:43:53 -0400, a écrit :

KeyRelease event, serial 105, synthetic NO, window 0x341,
 root 0x110, subw 0x0, time 1729143, (166,-8), root:(190,128),
 state 0x12, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES,
 XLookupString gives 0 bytes:
 XFilterEvent returns: False

KeyRelease event, serial 106, synthetic NO, window 0x341,
 root 0x110, subw 0x0, time 1729166, (166,-8), root:(190,128),
 state 0x10, keycode 164 (keysym 0x1008ff30, XF86Favorites), same_screen
YES,
 XLookupString gives 0 bytes:
 XFilterEvent returns: False

KeyPress event, serial 106, synthetic NO, window 0x341,
 root 0x110, subw 0x0, time 1729166, (166,-8), root:(190,128),
 state 0x10, keycode 164 (keysym 0x1008ff30, XF86Favorites), same_screen
YES,
 XLookupString gives 0 bytes:
 XmbLookupString gives 0 bytes:
 XFilterEvent returns: False

KeyRelease event, serial 106, synthetic NO, window 0x341,
 root 0x110, subw 0x0, time 1729168, (166,-8), root:(190,128),
 state 0x10, keycode 164 (keysym 0x1008ff30, XF86Favorites), same_screen
YES,
 XLookupString gives 0 bytes:
 XFilterEvent returns: False


That's very odd.  I guess this is due either to an upgrade of linux-2.6
or an upgrade of xserver-xorg-input-evdev.  At this stage I'd rather
think about linux-2.6.  Could you check in the linux console (without X)
what happens with showkey -s ? (here it shows 0x3a 0xba)

Samuel


It says UNICODE mode and the codes for caps lock are:

press: 0x3a 0xe0 0x66
repeat: 0x3a
release: 0xba 0xe0 0x

I also just discovered the right shift key goes back a page in 
iceweasel. Here are the right-shift codes:


xev:
KeyRelease event, serial 35, synthetic NO, window 0x481,
root 0x110, subw 0x0, time 876874940, (169,-12), root:(199,150),
state 0x11, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 35, synthetic NO, window 0x481,
root 0x110, subw 0x0, time 876874941, (169,-12), root:(199,150),
state 0x10, keycode 166 (keysym 0x1008ff26, XF86Back), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False


showkey -s:
press: 0x36 0xe0 0x6a
repeat: 0x36
release: 0xb6 0xe0 0xea

--
Tom Vier t...@triadsys.com
Senior Net/Sys Admin
Triad Systems Engineering, Inc.

703-956-1535 office
703-984-9093 cell
703-404-0308 helpdesk




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c7ff6f5.3080...@triadsys.com