Bug 358547 - Some Shortcuts get assigned to wrong keys (mixup between current and us layout)
Summary: Some Shortcuts get assigned to wrong keys (mixup between current and us layout)
Status: RESOLVED DUPLICATE of bug 355046
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_keys (show other bugs)
Version: 5.4.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Michael Jansen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-25 18:06 UTC by Arek Guzinski
Modified: 2018-10-01 20:09 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 Arek Guzinski 2016-01-25 18:06:16 UTC
I am on KUbuntu 15.10, using a slightly modified Version of the programmer dvorak layout. Escape is swapped with CapsLock.

here are my examples (best viewed with monospace fonts):
Action                  |   Keys Pressed and Displayed  |   Actual Keys Performing the Action
Log out                 |   Meta + CapsLock             |   Meta + Escape
Log out                 |   Meta + Escape               |   Meta + CapsLock
Window to Next Screen   |   Meta + Shift + Q            |   Meta + Shift + ; 
Window to Next Screen   |   Meta + :                    |   ??? 

So in order to map something to "Meta + Shift + ;" (';' is where 'q' is on us layout), i have to press "Meta + Shift + q" ('q' is where 'x' is on us).

i am sure more examples could be found...


Reproducible: Always

Steps to Reproduce:
1. Set Programmer Dvorak as your Main Keyboard Layout
2. Open Systemsettings -> Shortcuts -> Global Keyboard Shortcuts
3. Assign (e.g.) KWin -> Window to Next Screen to "Meta + Shift + ;"
4. Assign (e.g.) KWin -> Window to Desktop 1 to "Meta + Shift + q"

Actual Results:  
pressing Meta + Shift + ; moves the Window to Desktop 1

Expected Results:  
pressing Meta + Shift + ; should move the Window to the other Screen
Comment 1 Holger 2018-10-01 20:09:51 UTC

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