Everything running smooth, but no UP arrow?!

[KingKull2112]

I've had my system up and running for about 4 or 5 months now. I'm new to everything, but I've figured out what I need to get my system up and running. Now, when I first installed, I could use the up arrow. It took a few days and it stopped. I changed keyboards, it worked find, and it stopped again. I rarely use the up arrow, but this is getting to be a major annoyance now.

My system: Linux 2.6.32-5-686 #1 SMP i686 GNU/Linux
Removed the username and time stamp

Has anybody else had a problem like this? I googled it and found nothing for Debian. Any help is much appreciated

Also, before I forget, I didn't do any updates that would screw it up and its only the up arrow that doesn't work (Keypad up isn't good enough for some reason)

[cynwulf]

Open a terminal and do

xev

Try hitting the UP arrow key and see what appears.

[KingKull2112]

Open a terminal and do

xev

Try hitting the UP arrow key and see what appears.

This is what I got back

KeyPress event, serial 34, synthetic NO, window 0x3a00001,
    root 0x1ad, subw 0x0, time 611916931, (168,-7), root:(546,281),
    state 0x0, keycode 111 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XKeysymToKeycode returns keycode: 78
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x3a00001,
    root 0x1ad, subw 0x0, time 611917004, (168,-7), root:(546,281),
    state 0x0, keycode 111 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XKeysymToKeycode returns keycode: 78
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

I have no idea what it means

[cynwulf]

This is what I get on my VM here when I hit the up arrow:

KeyPress event, serial 34, synthetic NO, window 0x1200001,
    root 0x107, subw 0x0, time 931692, (214,394), root:(215,414),
    state 0x0, keycode 111 (keysym 0xff52, Up), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x1200001,
    root 0x107, subw 0x0, time 931769, (214,394), root:(215,414),
    state 0x0, keycode 111 (keysym 0xff52, Up), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

This is what I get for the scroll lock key:

KeyPress event, serial 34, synthetic NO, window 0x1200001,
    root 0x107, subw 0x0, time 937304, (214,394), root:(215,414),
    state 0x0, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x1200001,
    root 0x107, subw 0x0, time 937424, (214,394), root:(215,414),
    state 0x0, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

If you look at your output you will notice that while you are hitting the up arrow (keycode 111), the actual interpretation is "Scroll_Lock". So basically your up arrow is functioning as a scroll lock key. This is made obvious by that extra line in your output:

XKeysymToKeycode returns keycode: 78

Which means that 111 (up arrow) is symlinked to 78 (scroll lock).

How this has happened, I'm not sure. But there are a few areas you can look at. I would go for the easiest options first and suspect that something in your window manager / desktop environment has configured the key that way. Try creating another user, log in to an xsession as that user and see if the xev output remains the same.

[KingKull2112]

This is what I get on my VM here when I hit the up arrow:

KeyPress event, serial 34, synthetic NO, window 0x1200001,
    root 0x107, subw 0x0, time 931692, (214,394), root:(215,414),
    state 0x0, keycode 111 (keysym 0xff52, Up), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x1200001,
    root 0x107, subw 0x0, time 931769, (214,394), root:(215,414),
    state 0x0, keycode 111 (keysym 0xff52, Up), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

This is what I get for the scroll lock key:

KeyPress event, serial 34, synthetic NO, window 0x1200001,
    root 0x107, subw 0x0, time 937304, (214,394), root:(215,414),
    state 0x0, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x1200001,
    root 0x107, subw 0x0, time 937424, (214,394), root:(215,414),
    state 0x0, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

If you look at your output you will notice that while you are hitting the up arrow (keycode 111), the actual interpretation is "Scroll_Lock". So basically your up arrow is functioning as a scroll lock key. This is made obvious by that extra line in your output:

XKeysymToKeycode returns keycode: 78

Which means that 111 (up arrow) is symlinked to 78 (scroll lock).

How this has happened, I'm not sure. But there are a few areas you can look at. I would go for the easiest options first and suspect that something in your window manager / desktop environment has configured the key that way. Try creating another user, log in to an xsession as that user and see if the xev output remains the same.

The funny thing is? My scroll lock light doesn't turn on. I'm gonna see if I can reconfig the key bindings. I read somewhere that you can do that in one of the files, but I'm gonna look up how to do it cuz I have NO clue where to start lol. I'll let you know what I find.
Oh, and KDE ftw >_<

[KingKull2112]

Still not working. I submitted a bug report to KDE and they blew me off

Edit
I was actually looking around and from what I gather, I need to get into my keymap to edit it. Any tips?