Bug 240171 - sun type 7 keyboard, extra keys are not assignable
Summary: sun type 7 keyboard, extra keys are not assignable
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: shortcuts (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-31 06:32 UTC by dosnerd90
Modified: 2023-01-05 19:18 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 dosnerd90 2010-05-31 06:32:01 UTC
Version:           unspecified (using KDE 4.3.5) 
OS:                Linux

When I try too assign one of the following keys under standard keyboard settings I get a messagebox saying "The key you just pressed is not supported by Qt."
The keys are: Stop, Props, Front, Open, Find, Cut, Paste, Copy, Undo, Again.

Reproducible: Always

Steps to Reproduce:
Goto Standard Keyboard Shortcuts and click on any shortcut, then click custom and click the button to assign the key and type one of these keys: Stop, Props, Front, Open, Find, Cut, Paste, Copy, Undo, or Again

Actual Results:  
messagebox saying "The key you just pressed is not supported by Qt."

Expected Results:  
a messagebox saying "The key you just pressed is not supported by Qt."
Comment 1 Andriy Rysin 2010-06-01 03:23:22 UTC
Reassigning to kcm_keys
Comment 2 dosnerd90 2010-06-13 22:54:02 UTC
Under "Expected Results" I meant to say "key gets assigned".
Comment 3 Jekyll Wu 2012-12-04 05:18:33 UTC
I guess this can only be fixed by Qt itself.
Comment 4 Andrew Crouthamel 2018-11-09 01:05:08 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 5 Andrew Crouthamel 2018-11-20 04:05:59 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 6 Justin Zobel 2023-01-01 04:20:00 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 7 Andy Harrison 2023-01-01 21:09:51 UTC
I no longer have access to that type of keyboard, so moving this to resolved status.  No point in holding it open, I don't think they even make those keyboards anymore.
Comment 8 Jonathan Marten 2023-01-05 19:18:26 UTC
Putting this information here for reference:  I still use a Sun Type 6 keyboard (USB), with the very useful left keypad, and the same applies to the type 7.  The keys need to be both mapped to XFree86 keycodes and the keycodes need to be supported by Qt in order to be able to define them in KDE, see bug 220712.  The xmodmap script that I use is:

! Props
keycode 138 = XF86Option
! Open
keycode 142 = F17
! Front
keycode 140 = F15
! Audio
keycode 123 = XF86AudioRaiseVolume SunVideoRaiseBrightness
keycode 122 = XF86AudioLowerVolume SunVideoLowerBrightness
keycode 121 = XF86AudioMute SunVideoDegauss

All other keyboard keys (including Cut, Copy, Paste, Stop, Again, Undo, Find and Help) are supported as standard with current Qt.