SUMMARY When using the Hyper key as a modifier for keyboard shortcuts, it does not work. The shortcut selects Hyper as a single key press and will not accept secondary key presses to be modified. It essentially appears to be acting like an alpha-numeric key and not as a modifier. STEPS TO REPRODUCE 1. Open System Settings > Shortcuts 2. Selection category and option for shortcut 3. Hold Hyper key OBSERVED RESULT The waiting dialog for keyboard input will exit and garbage will be inserted into shortcut window. EXPECTED RESULT Allowed to continue finishing the shortcut with a non-modifier and modifier keys. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.1.1/Plasma 5.26.4 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Graphics Platform: X11 ADDITIONAL INFORMATION This is a dedicated Hyper key not a remap. Xkb is using a defined keyboard setup for this setup without a remap, as is the console driver, so the Hyper key works even on the console. I don't experience this type of problem under XFCE, Gnome, or any of the other Window Managers just under KDE Plasma.
Please try Wayland also
Created attachment 155097 [details] Image of resulting shortcut Here's a picture of the result when using Hyper.
(In reply to Andrey from comment #1) > Please try Wayland also Yes, the same happens under Wayland. I didn't test Wayland since there are still issues I've run into under it the last time using Plasma that drive me to the X11 edition. Ultimately it was this bug that sent me back to Gnome so I'm reporting it now in hopes someone with more understanding knows how to fix it. My understanding is that the underlying keyboard mechanism for Wayland and X11, XKB, is the same. So their interpretation would be the same wouldn't it?
Can you check if your bug is this, and if it is - you have the relevant Qt patch? https://bugreports.qt.io/browse/QTBUG-62102
Also note, according to the comment there: https://bugreports.qt.io/browse/QTBUG-62102?focusedCommentId=568808&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-568808 , you should still be able to register the shortcut on Wayland despite the odd ៀ? symbols
(In reply to Andrey from comment #4) > Can you check if your bug is this, and if it is - you have the relevant Qt > patch? > https://bugreports.qt.io/browse/QTBUG-62102 How would this apply if Meta (mod4, Super) works fine?
As you can see there, the patch is about Hyper, too: "qxkbcommon: Map Super/Hyper to Meta early enough to have an effect"
Also your problem might be related to this patch, I don't see it adds Syper/Hyper, though: https://codereview.qt-project.org/c/qt/qtbase/+/411073
(In reply to Andrey from comment #8) > Also your problem might be related to this patch, I don't see it adds > Syper/Hyper, though: > https://codereview.qt-project.org/c/qt/qtbase/+/411073 This doesn't appear to affect super, alt, ctrl for me and the bug apparently applies to Qt? And the "fix" is for me to program something? I'm just a user in this case. I'm not really familiar with Qt or KDE APIs. All these things happen. Since I don't see any of these things happen with Super I cannot imagine they are linked, but that's not for me to determine. I don't see an immediately patch there for me to apply that would easily be added to some package on my Arch machine or I might try it. Qt was just part of an update it looks like here, so it would've been possibly a good time to try. This issue *only* applies to Hyper. This issue *only& happens under Plasma/KDE. This issue does not happen under XFCE and it does not happen when using custom shortcuts in QT applications under XFCE. Hence the report. I'm not sure how this could apply because of that is all. That's just my input. If it is just *only* me, then there is that but it looks like others have seen this in the past. So it was my belief maybe this is one of those bugs that has resurfaced. Hence reporting.
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!
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!
I did some more fixing of these kinds of problems but need more info. Could you provide a reference to your keyboard or screenshot of the key? I thought there is no keyboards with physical Hyper nowadays..
It might be this patch will fix it, still I need more info requested above. https://codereview.qt-project.org/c/qt/qtbase/+/458395