Bug 294245 - Unsupported Key message when adding a custom Alt+Shift+<key> shortcut
Summary: Unsupported Key message when adding a custom Alt+Shift+<key> shortcut
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_khotkeys (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Michael Jansen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-16 16:26 UTC by Steven Franzen
Modified: 2023-02-11 03:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steven Franzen 2012-02-16 16:26:39 UTC
Version:           unspecified (using KDE 4.8.0) 
OS:                Linux

Upon adding a custom Alt+Shift+<key> shortcut in "Shortcuts and Gestures" or "Window Behavior" in the System Settings, the following message is displayed: "The key you just pressed is not supported by Qt". Coincidentally, while displaying this message box, all keyboard actions are suppressed for the rest of the system.

Additionally, in the System Settings > Window Behavior > Task Switcher screen, the Apply button is always greyed out, regardless of making a valid change in the settings. This behavior does not occur in the global System Settings > Shortcuts and Gestures screen.

Reproducible: Always

Steps to Reproduce:
1. Go to any keyboard shortcuts configuration screen, e.g. System Settings > Shortcuts and Gestures.
2. Try to set a custom shortcut containing the Alt and Shift keys.

Actual Results:  
Immediately upon holding Alt+Shift, the unsupported key message is displayed.

Expected Results:  
The Alt+Shift combination should be valid.

I am using the US International w/dead keys keyboard layout.
Comment 1 Steven Franzen 2013-01-13 21:59:33 UTC
I recently discovered that Alt + Shift was in use as the shortcut to change keyboard layouts, in the Input Devices settings, which triggers this error message immediately upon trying to use it in another shortcut. Changing or removing this shortcut resolved both this issue and the one in bug 294249 for me, but a clearer error message explaining the occupied shortcut would be useful. And perhaps there could be a short delay or other measure before "locking in" the new shortcut, so that e.g. Alt + Shift + Tab can be pressed without interruption by an error thrown for Alt + Shift.
Comment 2 Gregor Mi 2013-12-08 14:05:46 UTC
I have the same problem and solved it by assigning a different key (Alt + CAPS Lock, http://publicstatic.de/gnu/linux/images/2013-12-08-kde-keyboard-settings.png) for the keyboard layout switching.

Still the message Alt + Shift "is not supported by QT" is confusing (http://publicstatic.de/gnu/linux/images/2013-12-08-kde-taskswitcher-2.png). A more speaking message would be nice ("The shortcut is already assigned to another function").

> Coincidentally, while displaying this message box, all keyboard actions are suppressed for the rest of the system.

Same experience - Print screen for printing the message box did not work :)
Comment 3 Gregor Mi 2013-12-08 14:18:28 UTC
Sidenote: I experience the same behaviour as stated in this comment https://bugs.kde.org/show_bug.cgi?id=174142#c11:

The original/default shortcut is "Alt+Shift+Backtab". When it is reassigned manually by pressing Alt, Shift and Tab the new shortcut is displayed as "Alt+Shift+Tab" which seems more logical since "Backtab" implies that Shift was already pressed.
Comment 4 Andrew Crouthamel 2018-11-11 04:23:48 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-21 04:43:29 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-12 01:57:57 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 Bug Janitor Service 2023-01-27 05:07:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2023-02-11 03:52:00 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!