I had problems with my keyboard before, and I'm more and more convinced
that there's a bug *somewhere*. This is from xev, one press of the
PrintScreen key and one of the backslash key ('#' sign, German layout).>KeyPress event, serial 28, synthetic NO, window 0x2800001, > root 0x76, subw 0x0, time 6754199, (393,144), root:(397,876), > state 0x0, keycode 111 (keysym 0x23, numbersign), same_screen YES, > XLookupString gives 1 bytes: "#" > >KeyRelease event, serial 28, synthetic NO, window 0x2800001, > root 0x76, subw 0x0, time 6754199, (393,144), root:(397,876), > state 0x0, keycode 111 (keysym 0x23, numbersign), same_screen YES, > XLookupString gives 1 bytes: "#" > >KeyPress event, serial 28, synthetic NO, window 0x2800001, > root 0x76, subw 0x0, time 6754199, (393,144), root:(397,876), > state 0x0, keycode 111 (keysym 0x23, numbersign), same_screen YES, > XLookupString gives 1 bytes: "#" > >KeyRelease event, serial 28, synthetic NO, window 0x2800001, > root 0x76, subw 0x0, time 6754295, (393,144), root:(397,876), > state 0x0, keycode 111 (keysym 0x23, numbersign), same_screen YES, > XLookupString gives 1 bytes: "#" > >KeyPress event, serial 28, synthetic NO, window 0x2800001, > root 0x76, subw 0x0, time 6754295, (393,144), root:(397,876), > state 0x0, keycode 111 (keysym 0x23, numbersign), same_screen YES, > XLookupString gives 1 bytes: "#" > >KeyRelease event, serial 28, synthetic NO, window 0x2800001, > root 0x76, subw 0x0, time 6754295, (393,144), root:(397,876), > state 0x0, keycode 111 (keysym 0x23, numbersign), same_screen YES, > XLookupString gives 1 bytes: "#" > >KeyPress event, serial 28, synthetic NO, window 0x2800001, > root 0x76, subw 0x0, time 6759606, (393,144), root:(397,876), > state 0x0, keycode 111 (keysym 0x23, numbersign), same_screen YES, > XLookupString gives 1 bytes: "#" > >KeyRelease event, serial 28, synthetic NO, window 0x2800001, > root 0x76, subw 0x0, time 6759710, (393,144), root:(397,876), > state 0x0, keycode 111 (keysym 0x23, numbersign), same_screen YES, > XLookupString gives 1 bytes: "#" Notice the similarity? Also, on a console (under X), I get three '#' signs when pressing the PrintScreen key and a single one with the BKSL key (but only after modifying the X server's keysymbol file). On a text console, I had the BKSL key working after modifying something else which I forgot, now after an update, the key is toggling between the two recently used consoles again which makes editing scripts and config files on the console a royal PITA since I can't comment out anything. It's also one of the things Windows can do better, there it's working as a standard keyboard with all keys doing what's printed on them. It's a Cherry MY3000 USB keyboard, the error started occuring some time back with some late 2.4.x kernel and continues through to at least 2.6.3. Any ideas what I can do? ### (<-- the printscreen key ;-) ) -- Got Backup? Jabber: Shadowdancer at jabber.fsinf.de
pgp00000.pgp
Description: PGP signature
