Bug 204549

Summary:	When switching keyboard layouts, shortcuts are not moved
Product:	[Applications] systemsettings	Reporter:	Gaël de Chalendar (aka Kleag) <kleagg>
Component:	kcm_keyboard_layout	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	arysin, bruno.leon
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Mandriva RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Gaël de Chalendar (aka Kleag) 2009-08-20 18:12:27 UTC

Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    Mandriva RPMs

I use two keyboard layouts, default French Azerty and French Dvorak Bépo. The problem is that when switching from the primary one to the second one, shortcuts are not moved. 

For example, the Azerty "A" becomes "B" in Bépo. Thus if I hit Ctrl+A in Azerty to select all, I have to type Ctrl+B in Bépo.

So, probably shortcuts should be associated to the character typed and not to the physical keyboard key ?

This can be related to bug #83732, but I'm not sure it is exactly the same.

Comment 1 Bruno Léon 2009-08-29 18:43:21 UTC

Hi,

I can confirm thih behaviour under Kubunty Jaunty update to KDE 4.3.
The correct layout is not set when switching:

Setup:
- Kubuntu English default install
- Add French keyboard layout
- Switch to FR layout

Symptom:
- Press the letter A on the French keyboard correctly generates a A (Ok)
- Keyboard shortcut like CTRL+A will quit an application instead of doing
select all. So it is understood as CRTL+Q

Conclusion
I first believed this to be a bug in shorcuts but when I checked in system
settings, when you select the FR layout, what is actually done is:
setxkbmap -layout us,fr
when it should be
setxkbmap -layout fr,fr (This command fixed the problem for me)

I even do not understand how I can write in French with the default comman
d that is executed...

Comment 2 Andriy Rysin 2010-05-13 05:10:47 UTC

Unfortunately the shortcuts are handled by Qt so not much keyboard module or even KDE can do about it. You may file a bug against Qt. I actually think there was already a report for this problem but I could not find it quickly now.