On Fri, Sep 03, 2010 at 01:46:04PM -0800, James Zuelow wrote: > ----Original Message---- > From: James Zuelow [mailto:james_zue...@ci.juneau.ak.us] > Sent: Thursday, August 26, 2010 4:31 PM > To: debian-user@lists.debian.org > Subject: RE: Arrow keys won't scroll history in squeeze konsole/bash > > ----8<---snip---8<---- > > > > I'm not the only one seeing this: > > > > http://www.linuxquestions.org/questions/linux-general-1/kde4-up-key-stops-working-sporadically-828016/ > > > > Unlike the author of that post, I haven't remapped any of my keys. > > Everything should be stock. > > > ----8<---snip---8<---- > > > > How I can reproduce: > > > > 1) Log in to KDE. The up arrow works fine. > > 2) Log out of KDE. Log back in again. The up-arrow does not work. > > 3) Log out of KDE, and restart the X server. Log back in, the up > > arrow works. > > > > Repeat. > > > > So I work around it by restarting the X server before I log in -- the > > up arrow will work for the FIRST login session. After that it will > > be ignored until I restart the X server again. > > OK, apparently I'm the only person seeing this on the mailing list. Unlike > the author of the linuxquestions report above, changing my keyboard map does > NOT help me. I still get the same problem regardless. > > Now a question for the list: > > Which package should I file a bug against? Between Xorg and KDE I'm not sure > where to start -- although I'm pretty sure it's a KDE thing and not X. > Plasma desktop? Or is there some subcomponent of KDE that handles the > keyboard specifically?
I have been experiencing this issue since I upgraded this box to KDE4, although there have been updates in X also. My workaround has been tweaking a xmodmap file I load the fisrt time I start konsole (xmodmap xmodmap.txt). Some things doesn't work OK yet, but makes things usable at the very least. (Many screen apps honor vi-style keys, so you can navigate using hjkl). Anyway, as a screen user, this is a real PITA, also, vi in command mode lacking AltGr makes difficult even to comment a line out: I gotta enter visual, copy the character and paste it afterwards. I can confirm that ouside X the keyboard behaves correctly, so I have been using xev to see what is going on. Some keys (AltGr, in this example) send <b>two</b> different events with different keycodes: KeyPress event, serial 40, synthetic NO, window 0x2e00001, root 0x15a, subw 0x0, time 3950562, (378,154), root:(1265,306), state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False MappingNotify event, serial 40, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 KeyPress event, serial 40, synthetic NO, window 0x2e00001, root 0x15a, subw 0x0, time 3950562, (378,154), root:(1265,306), state 0x90, keycode 113 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False MappingNotify event, serial 42, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 KeyRelease event, serial 42, synthetic NO, window 0x2e00001, root 0x15a, subw 0x0, time 3950647, (378,154), root:(1265,306), state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False MappingNotify event, serial 42, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 KeyRelease event, serial 42, synthetic NO, window 0x2e00001, root 0x15a, subw 0x0, time 3950647, (378,154), root:(1265,306), state 0x10, keycode 113 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False For cursor keys, I remapped my xmodmap.txt to use only one of those keycodes, mapping the other to an empty string (example with cursor down): KeyPress event, serial 36, synthetic NO, window 0x2e00001, root 0x15a, subw 0x0, time 4421665, (210,-23), root:(1056,0), state 0x10, keycode 116 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False MappingNotify event, serial 36, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 KeyPress event, serial 36, synthetic NO, window 0x2e00001, root 0x15a, subw 0x0, time 4421665, (210,-23), root:(1056,0), state 0x10, keycode 104 (keysym 0xff54, Down), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False MappingNotify event, serial 38, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 KeyRelease event, serial 38, synthetic NO, window 0x2e00001, root 0x15a, subw 0x0, time 4421733, (210,-23), root:(1056,0), state 0x10, keycode 116 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False MappingNotify event, serial 38, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 KeyRelease event, serial 38, synthetic NO, window 0x2e00001, root 0x15a, subw 0x0, time 4421737, (210,-23), root:(1056,0), state 0x10, keycode 104 (keysym 0xff54, Down), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False $ egrep "(116|104)" xmodmap.txt keycode 104 = Down NoSymbol Down keycode 116 = Note that I'm no expert in this, and the whole xkb system is somewhat an obscure area for me. I would also need some help to figure out what's the problem here. Obviously, there is a bug. To find out if it belongs to KDE or X, one should install another box with another DE, I guess. Sorry for the long post. HTH. -- Huella de clave primaria: 0FDA C36F F110 54F4 D42B D0EB 617D 396C 448B 31EB
signature.asc
Description: Digital signature