Bug 380888

Summary: Modifier-only shortcuts are impossible to configure
Product: [Plasma] plasmashell Reporter: Szczepan Hołyszewski <rulatir>
Component: generalAssignee: David Edmundson <kde>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bshah, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.10.0   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Szczepan Hołyszewski 2017-06-06 12:14:14 UTC 
Modifier-only shortcuts, theoretically supported since 5.8, are impossible to configure with GUI as of 5.10.

Steps to reproduce:

1. Go to systemsettings5/Workspace/Shortcuts/Global Shortcuts
2. Select Plasma from the Component list, then "Activate interface element: Application Dashboard" [NOTE: this is a back-translation from Polish, I couldn't figure out how to force systemsettings5 to show this particular tree view in English]
3. Switch to Custom and/or clear the current shortcut if necessary
4. Press the "None" button to initiate shortcut input
5. Press and release Right Win

Expected result:

Right Win should be set as a modifier-only keyboard shortcut

Actual result:

When the Right Win is pressed, the button displays "Meta+...". When the Right Win is subsequently released, the button reverts to "None". The modifier-only keyboard shortcut is not set.
Comment 1 Szczepan Hołyszewski 2017-06-06 12:45:52 UTC 
ERRATA

Wherever the above description says Right Win, it should have said Left Win instead, because that's the shortcut I actually tried to assign.

Additionally, in the Actual results section the button reverts to "Input...", not to "None", after Left Win is released.

Apologies for inaccurate initial description - I was working from memory and wasn't actually alternating between performing each individual step and describing it here.

Also, I'd like to express my deepest compassion to the KDE team who in 2017 are still stuck with an ancient bugtracker that doesn't allow the submitter to edit the original description to fix a stupid mistake.
Comment 2 Christoph Feck 2017-06-21 14:56:52 UTC 

*** This bug has been marked as a duplicate of bug 371323 ***