Bug 362775

Summary:	must set shortcuts like on a qwerty layout on a azerty layout
Product:	[Frameworks and Libraries] frameworks-kglobalaccel	Reporter:	nomood <ludwig.schubert>
Component:	general	Assignee:	kdelibs bugs <kdelibs-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	nate, raphael.kde, stophe72.d
Priority:	NOR
Version First Reported In:	5.49.0
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description nomood 2016-05-07 10:00:38 UTC

hi there !
When I want to set some shortcuts I have to do it like if  I had a qwerty layout but I have a azerty layout with french layout set in input device.
Ex: when I set a shortcut like 'ctrl+a' I have to do 'ctrl+q' to trigger it ....

It is very disturbing and I can't set some of my shortcuts because of that.
For example  if I want to put a shortcut on "ctrl+<" it doesn't work and I can't find wich combinaison will do the trick.

Thanks.

Reproducible: Always

Comment 1 Stophe 2016-12-15 07:21:45 UTC

Hi,

Same issue on Archlinux Kde 5.8.4. I am French, so I use an Azerty Keyboard.
In Input Devices, keyboard is set to [fr, Français, Français (Azerty), fr, ]

I would like to launch:
- Android Studio with [WIN][SHIFT][a], but i must use [WIN][SHIFT][q] to setup shortcut
- MySqlWorkbench with [WIN][SHIFT][w], but i must use [WIN][SHIFT][z] to setup shortcut

Custom shortcuts kcm plugin seems to confuse Azerty layout with Qwerty.

I don't have to behavior with Lxqt or Openbox

Comment 2 Stophe 2016-12-22 10:09:44 UTC

Same issue on Arch Linux KDE 5.29
Sometimes kshortcut confuse keyboard layouts.
Ex : 
- I launch Android Studio with [WIN][SHIFT][a], but actually I have to setup shortcut to [WIN][SHIFT][q] for working
- I launch MySkqWorkbench with [WIN][SHIFT][w], but actually I have to setup shortcut to [WIN][SHIFT][w] for working
- I use [WIN][!] to vertically maximize, but today, it doesn't (I don't know where is [!] on Qwerty keyobard :)

Comment 3 Nate Graham 2018-08-28 19:32:48 UTC

*** Bug 397984 has been marked as a duplicate of this bug. ***

Comment 4 Nate Graham 2018-11-02 13:52:15 UTC


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