Bug 256670 - Keyboard shortcuts stop working if US layout is not on top
Summary: Keyboard shortcuts stop working if US layout is not on top
Status: RESOLVED UPSTREAM
Alias: None
Product: kxkb
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Andriy Rysin
URL:
Keywords:
: 226790 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-11-12 11:05 UTC by Nikita Churaev
Modified: 2010-12-01 11:07 UTC (History)
3 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 Nikita Churaev 2010-11-12 11:05:09 UTC
Version:           unspecified
OS:                Linux

Keyboard shortcuts stop working if US layout is not on top of the layout list.

Reproducible: Always

Steps to Reproduce:
1. Open keyboard settings
2. Add Russian and US layout
3. Move Russian layout on top of the list
   * ru
   * us
4. Apply changes
5. Open Kate
6. Write some text
7. Press Ctrl+Z 

Actual Results:  
It does not undo the changes

Expected Results:  
It should undo the changes
Comment 1 Nikita Churaev 2010-11-12 11:08:19 UTC
It doesn't work even if I switch to US layout
Comment 2 Kai Uwe Broulik 2010-11-13 00:03:37 UTC
I just noticed that when I have both DE and NEO enabled that the < or > key does not work. But don‘t know if this is directly related to that.
Comment 3 Leonidas Arvanitis 2010-11-13 17:54:23 UTC
I can confirm using Greek layout. Whenever US is not the first layout keyboard shortcuts stop working in all programs using _any_ layout.

KDE 4.5.3
Qt 4.7.0
(K)Ubuntu 10.10
Comment 4 Nikita Churaev 2010-11-14 10:58:54 UTC
I think this is Qt bug since GTK applications handle this correctly
Comment 5 Andriy Rysin 2010-11-14 18:31:47 UTC
Unfortunately KDE keyboard module can't help here, it's how the shortcuts are handled in Qt. You can try to file a bug at http://bugreports.qt.nokia.com
Comment 6 Andriy Rysin 2010-12-01 11:07:55 UTC
*** Bug 226790 has been marked as a duplicate of this bug. ***