Fedora Account System
Red Hat Associate
Red Hat Customer
When I upgraded to Fedora 18, dead keys stopped working in Qt apps. For example, I was not able to type ê using ^ then e as I did before. (I am using GNOME as my main desktop.) I just found out that installing package ibus-qt fixes the problem. I think this package should have been installed by default during the upgrade, but it wasn't. Is this specific to my system, or should something be changed like Qt recommending ibus-qt?
If you are using IBus, you should have installed ibus-qt from the beginning. There's no upgrade path issue there. And if you aren't using IBus, then installing ibus-qt is the wrong fix for your real issue (the broken dead keys). And we cannot require ibus-qt because it shouldn't be dragged in on setups without input methods. (We don't have Suggests nor Recommends in Fedora.)
No, I've never used IBus and I don't know much about it. I'm French, so I'm using a French layout FWIW. So maybe installing ibus-qt is the wrong fix, but at least it is a workaround. All I can say is that dead keys stopped working in F18 in Qt apps and that installing ibus-qt seems to fix it. I have never messed with input methods in any way. Please just ask if you want me to do some debugging to understand what happened.
OK, the problem is that QT_IM_MODULE=ibus even for new accounts and after a restart, with ibus-qt *removed*. Though the intended behaviour is QT_IM_MODULE=xim, cf. bug 70137. I don't understand how this is possible, since xinputrc and ibus.conf both contain: if test -f /usr/lib/qt4/plugins/inputmethods/libqtim-ibus.so || \ test -f /usr/lib64/qt4/plugins/inputmethods/libqtim-ibus.so; then QT_IM_MODULE=ibus else QT_IM_MODULE=xim fi and none of these files exist. $ grep -R ibus /etc/X11 /etc/X11/xinit/xinputrc:XIM=ibus /etc/X11/xinit/xinputrc:XIM_PROGRAM="/usr/bin/ibus-daemon" /etc/X11/xinit/xinputrc:ICON="ibus" /etc/X11/xinit/xinputrc:PREFERENCE_PROGRAM=/usr/bin/ibus-setup /etc/X11/xinit/xinputrc:GTK_IM_MODULE=ibus /etc/X11/xinit/xinputrc:if test -f /usr/lib/qt4/plugins/inputmethods/libqtim-ibus.so || \ /etc/X11/xinit/xinputrc: test -f /usr/lib64/qt4/plugins/inputmethods/libqtim-ibus.so; /etc/X11/xinit/xinputrc: QT_IM_MODULE=ibus /etc/X11/xinit/xinput.d/ibus.conf:XIM=ibus /etc/X11/xinit/xinput.d/ibus.conf:XIM_PROGRAM="/usr/bin/ibus-daemon" /etc/X11/xinit/xinput.d/ibus.conf:ICON="ibus" /etc/X11/xinit/xinput.d/ibus.conf:PREFERENCE_PROGRAM=/usr/bin/ibus-setup /etc/X11/xinit/xinput.d/ibus.conf:GTK_IM_MODULE=ibus /etc/X11/xinit/xinput.d/ibus.conf:if test -f /usr/lib/qt4/plugins/inputmethods/libqtim-ibus.so || \ /etc/X11/xinit/xinput.d/ibus.conf: test -f /usr/lib64/qt4/plugins/inputmethods/libqtim-ibus.so; /etc/X11/xinit/xinput.d/ibus.conf: QT_IM_MODULE=ibus Any ideas?
I think you use GNOME. gnome-settings-daemon sets QT_IM_MODULE=ibus whether ibus-qt is installed or not: https://git.gnome.org/browse/gnome-settings-daemon/tree/gnome-settings-daemon/main.c#n274 For non-GNOME desktops, QT_IM_MODULE=ibus is set if libqtim-ibus.so is installed in /etc/X11/xinit/xinput.d/ibus.conf
Yes GNOME unconditionally sets that env var. But I can't reproduce this problem here. If I remove ibus-qt I can still use dead keys in Qt applications even with the env var set to "ibus".
Interesting. Have you restarted your computer? OTOH, here if I start a Qt app with QT_IM_MODULE=xim, I still cannot input dead keys. So it looks like only installing ibus-qt fixes the issue. I've tried using a Portuguese and a German keyboard, and the same bug happens. Is there anything else I can do to debug this?
So as per comment #6, let's reassign this back to Qt. (But of course I cannot reproduce this issue here!)
(In reply to Milan Bouchet-Valat from comment #6) > Interesting. Have you restarted your computer? OTOH, here if I start a Qt > app with QT_IM_MODULE=xim, I still cannot input dead keys. So it looks like > only installing ibus-qt fixes the issue. > > I've tried using a Portuguese and a German keyboard, and the same bug > happens. > > Is there anything else I can do to debug this? Which key sequences you tried to type actually? You can show the current XKB keymaps: % setxkbmap -query I think QT_IM_MODULE=xim enables dead keys. % env QT_IM_MODULE=xim strace konsole --nofork |& grep inputmethods open("/usr/lib/qt4/plugins/inputmethods/libqimsw-multi.so", O_RDONLY|O_CLOEXEC) = 19
I have tried ^ and ¨ (no matter what's the next letter since the symbols are immediately printed). Does this give any useful information? $ setxkbmap -query rules: evdev model: evdev layout: fr,ml,us variant: oss,, $ env QT_IM_MODULE=xim strace konsole --nofork |& grep inputmethods stat("/usr/lib64/qt4/plugins/inputmethods/.", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 openat(AT_FDCWD, "/usr/lib64/qt4/plugins/inputmethods", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 9 statfs("/usr/lib64/qt4/plugins/inputmethods/", {f_type="EXT2_SUPER_MAGIC", f_bsize=4096, f_blocks=9820524, f_bfree=4659886, f_bavail=4559824, f_files=2506752, f_ffree=2148723, f_fsid={-660473973, 326774785}, f_namelen=255, f_frsize=4096}) = 0 lstat("/usr/lib64/qt4/plugins/inputmethods", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 lstat("/usr/lib64/qt4/plugins/inputmethods/libqimsw-multi.so", {st_mode=S_IFREG|0755, st_size=29048, ...}) = 0 stat("/usr/lib64/qt4/plugins/inputmethods/libqimsw-multi.so", {st_mode=S_IFREG|0755, st_size=29048, ...}) = 0 stat("/usr/lib64/kde4/plugins/inputmethods/.", 0x7fff53604240) = -1 ENOENT (No such file or directory) stat("/usr/lib/kde4/plugins/inputmethods/.", 0x7fff53604240) = -1 ENOENT (No such file or directory) stat("/usr/bin/inputmethods/.", 0x7fff53604240) = -1 ENOENT (No such file or directory)
(In reply to Milan Bouchet-Valat from comment #9) > I have tried ^ and ¨ (no matter what's the next letter since the symbols are > immediately printed). I can reproduce your problem now as could not do yesterday.
I'm also suffering this bug. Thanks for the workaround of ibus-qt. BTW I found this happening too on some Wine apps, but installing ibus-qt does not fix it. Can that be the same issue?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
What happens in F19 or later?
The same. For example, I am on XFCE and I open TortoiseHg (Qt) and then I write there with accents and, for example, "opción" becomes "opci´on". I found this workaround: Write "opci", then click elsewhere or change focus to other program, then click there again to continue writing, then write "ón". Weird. I use F19, and I installed XFCE after having GNOME, because GNOME does not work with FreeNX.
Thanks for the feedback, bumping Version to 19 so the bug stays open.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 and still the same problem. Please somebody update the version.
Well... not exactly the same problem. In F21 there's no ibus-qt package! Is there any other workaround?
(In reply to Yajo from comment #18) > Well... not exactly the same problem. In F21 there's no ibus-qt package! Is > there any other workaround? Forget this, it was my fault.
Raised to F21.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
F22 still equal.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.