Bug 353926 - Global shortcuts using wrong layout
Summary: Global shortcuts using wrong layout
Status: RESOLVED DUPLICATE of bug 350816
Alias: None
Product: frameworks-kglobalaccel
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Martin Flöser
URL:
Keywords:
: 355729 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-10-15 13:33 UTC by Marc Cousin
Modified: 2018-11-02 13:52 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Cousin 2015-10-15 13:33:03 UTC
I'm using two mappings from which I switch regularly: fr-azerty and fr-bepo (a kind of dvorak for french). I start with bepo, which is active most of the time. My X defaults to bepo:
    Option              "XkbLayout" "fr"
    Option              "XkbVariant" "bepo"


When I use keyboard shortcuts and the bepo is activated, global shortcuts are mapped to the azerty position. For instance, for locking, Ctrl+Alt+L is on bepo's R location (which is the azerty L location). Shortcuts are placed correctly when I am using the azerty mapping.

Bepo is my first mapping in KDE's keyboard preferences.



Reproducible: Always


Actual Results:  
Shortcuts should follow mapping
Comment 1 David Edmundson 2015-10-16 00:18:18 UTC
I'm confused, can you make sure I have this right:

you have bepo active

if you press "L" on the keyboard you get an "r" printed in an editor.

pressing control+alt+L locks the screen, whereas it should be control+alt+whatever L In Bepo is ?
Comment 2 Marc Cousin 2015-10-16 14:49:18 UTC
That's right.
Comment 3 Marc Cousin 2015-10-20 11:53:48 UTC
It's getting a bit weirder. It seems that when I plug an additional keyboard (when at home, with the docking station), the layout is correct on this additional keyboard.
Comment 4 Thomas Lübking 2015-10-25 11:24:01 UTC
experimental workaround, feel free to try https://git.reviewboard.kde.org/r/125786/
Comment 5 Thomas Lübking 2015-12-24 21:45:02 UTC
*** Bug 355729 has been marked as a duplicate of this bug. ***
Comment 6 Holger 2015-12-25 22:11:35 UTC
I was pointed here by Thomas Lübking:
https://forum.kde.org/viewtopic.php?f=289&t=130179&p=348185#p348185

In my case, the wrong mappings are tied to passwordless autologin on boot (as I'm using harddrive encryption and typing one password is enough for my taste.) That is, can someone reproduce wrong global shortcut mappings, after explicitly logging out, selecting his account and logging in again?
Comment 7 barbaker 2016-03-01 02:14:59 UTC
My Keyboard Layout is:

Map    us
Layout   English (US)
Variant   English (Dvorak)


All keyboard input uses the Dvorak variant on boot. Also:
My Application Keyboard Shortcuts use the Dvorak variant on boot 
My Global Keyboard Shortcuts use the Dvorak variant on boot
My Custom Shortcuts (Konsole Meta+T etc) do NOT use the Dvorak variant on boot but only the English (US) layout.

Like Holger, I use passwordless autologin on boot. If I log out and log in again the Custom Shortcuts DO use the Dvorak variant of English (US).  

I have set a separate password for KDE though, at the moment, I am the only user. But I have used autologin with KDE4 and the Dvorak variant of my Custom Shortcuts has always worked.

If it's any help (I'm not a programmer) kglobalshortcutsrc says:


[khotkeys]
_k_friendly_name=KDE Daemon
{7bc41141-af1b-4d8b-881e-ef505bc7ed9a}=Meta+D,none,New Action
{acb5bba1-0558-4acc-92bf-6451060320b5}=Meta+G,none,New Action
{cc2cb7bf-5df6-44b5-b820-1edd0234390f}=Meta+T,none,Konsole
{ce5de1dd-67c2-451e-955e-ac658371fbcf}=Meta+C,none,New Action


Reproducible: Always
Comment 8 Marc Cousin 2016-04-03 22:17:05 UTC
Yeah, same for me, passwordless login…
Comment 9 Holger 2016-07-25 13:01:38 UTC
@Martin Gräßlin

This is on status "NEEDSINFO WAITINGFORINFO"

Can you specify, which info is missing?

Thanks
Comment 10 Martin Flöser 2016-08-01 06:52:35 UTC
changing to unconfirmed.
Comment 11 Nate Graham 2018-11-02 13:52:51 UTC

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