After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 710126 - Qt5 apps don't react to changing keyboard layouts under GNOME
Qt5 apps don't react to changing keyboard layouts under GNOME
Status: RESOLVED FIXED
Product: libgnomekbd
Classification: Core
Component: Config
unspecified
Other Linux
: Normal normal
: ---
Assigned To: libgnomekbd maintainers
Sergey V. Udaltsov
Depends on:
Blocks:
 
 
Reported: 2013-10-14 17:30 UTC by pditchev
Modified: 2014-06-14 10:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description pditchev 2013-10-14 17:30:20 UTC
https://bugreports.qt-project.org/browse/QTBUG-34005 - the bug in Qt bug tracker

So simply put - build a Qt5 app (with some line input or whatever) , start it , change the layout - system-wide it changes , but the app continues using the layout it was started with . (all that in GNOME . In XFCE for example it doesn't happen) . My system is Manjaro , but I've had the same problem in Ubuntu .

The communication so far - I've made some tests according to the instructions from one of the Qt developers , and one of the GNOME developers stated an opinion that the problem is Qt related . Here's all the posts :
http://lists.qt-project.org/pipermail/development/2013-August/012822.html
http://lists.qt-project.org/pipermail/development/2013-August/012824.html
http://lists.qt-project.org/pipermail/development/2013-August/012827.html
http://lists.qt-project.org/pipermail/development/2013-September/012848.html
http://lists.qt-project.org/pipermail/development/2013-September/012849.html

https://mail.gnome.org/archives/desktop-devel-list/2013-September/msg00046.html

Related bugs according to one of the posts :
https://bugreports.qt-project.org/browse/QTBUG-30911
https://bugs.freedesktop.org/show_bug.cgi?id=23202
Comment 1 pditchev 2014-06-14 10:22:04 UTC
I don't know what fixed it, but the bug is gone for a week or so now.