Bug 221027 - QT apps have inconsistent behaviour for modifier keys when multiple layout switching is enabled
Summary: QT apps have inconsistent behaviour for modifier keys when multiple layout sw...
Status: RESOLVED UPSTREAM
Alias: None
Product: kxkb
Classification: Miscellaneous
Component: general (show other bugs)
Version: 2.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Andriy Rysin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-02 21:14 UTC by Mark Williamson
Modified: 2010-02-26 15:20 UTC (History)
0 users

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 Mark Williamson 2010-01-02 21:14:02 UTC
Version:           2.0 (using 4.3.4 (KDE 4.3.4), 4.3.4-3.fc12 Fedora)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.31.9-174.fc12.x86_64

Example:
Add UK/Default and UK/Dvorak layouts to the keyboard switcher choices.
Switch to UK/Dvorak.
Typing in a QT app behaves as expected.
In, e.g. Konversation, Ctrl+W (corresponding to a , key on my QWERTY keyboard) moves me left a tab, instead of closing it.  i.e. it behaves as if I'm in QWERTY layout.
In, e.g. Firefox, the same key combo closes a tab (expected behaviour).

I do not have layout switching whilst Ctrl is held enabled, so this is not expected behaviour.  The inconsistent behaviour between QT and non-QT has basically made it impossible for me to use layout switching.  I have read hints that it may be a bug in QT and not kxkb in which case I apologise for reporting here.

I have not tracked down anything very definitive so far - it's persisted over multiple versions of QT for me.  I am not sure how I would isolate this as a QT problem or where to report that.
Comment 1 Andriy Rysin 2010-02-21 02:18:44 UTC
This can't be helped by kxkb, this is Qt problem and there's corresponding bug report here http://bugreports.qt.nokia.com/browse/QTBUG-4845
Comment 2 Mark Williamson 2010-02-26 15:20:29 UTC
@Andriy Rysin:

Thanks for the link!  I had seen comments to the effect that it was a QT bug when searching elsewhere but didn't have much success in discovering anything beyond that.  I'm now watching the QT bug and updating information there; thank you for the link and sorry for the noise here!