Bug 354253 - Windows key can not be addressed
Summary: Windows key can not be addressed
Status: RESOLVED WORKSFORME
Alias: None
Product: khotkeys
Classification: Unmaintained
Component: general (show other bugs)
Version: 5.4.2
Platform: Debian unstable Linux
: NOR major
Target Milestone: ---
Assignee: Michael Jansen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-23 12:59 UTC by bluelupo
Modified: 2021-02-16 04:33 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 bluelupo 2015-10-23 12:59:13 UTC
Each scale as key combination with the Windows key and any other such as Win + X is not working. The Windows key appears from khotkeys not be approachable.

The error occurred here reproducible on two different KDE installations.

Placed action in the system settings:
Calling "Shortcuts/Custom Shortcuts", right-clicking in the middle field, on the context menu "New/Global Shortcut/Command-URL" is selected and an "Action" Tab deposited eg starting a console (konsole --profile "Shell"). In the tab "Trigger" the shortcut "Win + X" is entered.

Note: The tool xev recognizes the Windows key and correct time to a keycode.

Reproducible: Always

Steps to Reproduce:
see above

Actual Results:  
It can not create a shortcut to the Win key


system info:
Distro: siduchtion (based on Debian Unstable)
Kernel: 4.2.3-towo.1-siduction-amd64

khotkeys version:
khotkeys            4:5.4.2-1
khotkeys-data  4:5.4.2-1
Comment 1 Thomas Lübking 2015-12-24 21:40:20 UTC
Is this only a khotkeys problem, not affecting other global shortcuts (eg. to show krunner etc.)?

Please notice that config writing pre-5.5 is known to be buggy, so please ensure to check whether the issue remains with 5.5.
Comment 2 Justin Zobel 2021-01-17 07:06:58 UTC
As this bug was reported a long time ago, can you please test and confirm if this issue is still occurring.

I've set this bug to NEEDSINFO. Once you have added the required information please change the bug back to REPORTED so we know it's ready for investigation or RESOLVED/WORKSFORME if the issue is now resolved.
Comment 3 Bug Janitor Service 2021-02-01 04:33:13 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 4 Bug Janitor Service 2021-02-16 04:33:13 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!