Bug 292596 - Up arrow is NOT working, is coming back as Scroll Lock
Summary: Up arrow is NOT working, is coming back as Scroll Lock
Status: RESOLVED FIXED
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.6
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-27 14:55 UTC by Ben L
Modified: 2020-09-28 23:05 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben L 2012-01-27 14:55:12 UTC
Version:           4.6 (using KDE 4.4.5) 
OS:                Linux

I've gotten pretty far with this, I've done xev on it and here's 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


This is what somebody else got back and their up arrow works just fine


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 they got for scroll lock


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

My scroll lock button doesn't light up, either
Some how, KDE symlinked the up arrow to scroll lock. Is there anyway I can change this myself?

Reproducible: Always

Steps to Reproduce:
Press the up arrow on any window

Actual Results:  
Nothing

Expected Results:  
Page to scroll up or in the console, scroll through the last used command(s)

I'm not sure my version numbers, so
Qt: 4.6.3
KDE Development Platform: 4.4.5 (KDE 4.4.5)
KDE Daemon: $Id: kded.cpp 1031637 2009-10-05 16:58:19Z lunakl $

Also, when I got this keyboard, it worked just fine. This is the second keyboard I've had for this computer, and had the same system installed.
Comment 1 Christoph Feck 2012-01-27 17:55:44 UTC
Is this issue also present, it you log into a freshly created user account?
Comment 2 Ben L 2012-01-28 06:11:04 UTC
I would assume it doesn't, because the up arrow /does/ work in the command line when I close KDE. I looked up how to create a new account, but for some reason, I can't make a new user (I know you have to open it as root, but I don't have the option)
http://wiki.oseems.com/operatingsystem/kubuntu/add-new-user
Comment 3 Andrew Crouthamel 2018-11-06 15:03:43 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-17 04:53:21 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Nate Graham 2020-09-28 23:05:01 UTC
No response; assuming it was fixed since then.