Description of problem: Not able to type Japanese in "Add Card" Dialog or search bar in "Browse" window. Version-Release number of selected component (if applicable): Name : anki Version : 2.1.15 Release : 1.fc30 How reproducible: Steps to Reproduce: 1. Open Anki > "Add" 2. Type "aaa" with Anthy input Actual results: aaa Expected results: あああ Additional info: Input method works in GNOME applications like gedit, gnome-terminal. telegram-desktop has the same problem.
For some time I was able to fix this by exporting `QT_IM_MODULE=ibus`. This workaround does not work anymore.
I can reproduce the problem in Fedora 30. So far, it looks like that it affects all QT applications: - QT5 examples like https://doc.qt.io/qt-5/qtwidgets-widgets-lineedits-example.html - PyQT5 examples like https://pythonspot.com/pyqt5-textbox-example/ - kwrite, konsole - affects the ibus input methods (like Anthy or Pinyin) work in QT-based applications (gedit, ...) - switching between basic keyboard layouts (German, US, ...) works fine - I'm using the Cinnamon Desktop Environment - ibus-specific environment variables are set: QT_IM_MODULE=ibus XMODIFIERS=@im=ibus So far I'm pretty sure that's not an Anki issue. However, I don't know which exact components is causing the problem. Candidates are - qt5 - qt5-base - ibus-qt - ... I'm setting the component to qt5-base, because this source package builds qt5-qtbase-gui which includes /usr/lib64/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so ...
After some more research it turned out that the problem was already reported: ibus: https://github.com/ibus/ibus/issues/2137 it turned out to be an glib2 issue: https://gitlab.gnome.org/GNOME/glib/issues/1831 there is a merge request for glib2 available: https://gitlab.gnome.org/GNOME/glib/merge_requests/1176 I tested the proposed changes https://gitlab.gnome.org/GNOME/glib/merge_requests/1176/diffs with glib2-2.60.7-1.fc30.x86_64 and applying them solves the issue. Please consider to integrate this patch to Fedora's glib2 package. Until that's fixed, there won't be any ibus-based input methods (e.g. for Japanese, Chinese, ...) available in QT5-based apps. Setting the component now to glib2...
The mentioned merge request was now merged into glib2-master upstream: https://gitlab.gnome.org/GNOME/glib/merge_requests/1176/commits The changes were backported upstream at least to glib-2-62 branch: https://gitlab.gnome.org/GNOME/glib/merge_requests/1194 The issue is quite generic. From upstream bug report https://gitlab.gnome.org/GNOME/glib/issues/1831 : "Short summary: From time to time a GDBusServer responds with REJECTED EXTERNAL to new connections on a private socket." Please consider to cherry-pick the commits to fix the issue in F30, too.
I have same issue with Fedora 31 with KDE desktop.
glib2-2.62.1-1.fc31.x86_64 ibus-1.5.21-3.fc31.x86_64
Just to note I believe the regression is due to recent CVE fixes that went into ibus.
Since this is a CVE issue, I'd request to back-port the fix to Fedora 31, Fedora 30 and Fedora 29.
@glib2 maintainers: Please can you have a look at this issue? Are you interested in a merge request to backport the mentioned upstream bug fix? It looks like that other distributions backported the changes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941018
FEDORA-2019-9ff4e37cb3 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-9ff4e37cb3
Due to scheduling, we decided to wait a few days for glib 2.62.3 before preparing a F31 update. Please make sure to reopen this bug if bodhi closes it if the F30 update lands before the F31 update is ready.
glib2-2.60.7-2.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-9ff4e37cb3
(In reply to Michael Catanzaro from comment #11) > Due to scheduling, we decided to wait a few days for glib 2.62.3 before > preparing a F31 update. Please make sure to reopen this bug if bodhi closes > it if the F30 update lands before the F31 update is ready. OK, I understood what you meant. Thank you for fixing F30 too.
Updating to glib2-2.60.7-2.fc30.x86_64 fixed my input problems with anki and telegram-desktop :)
glib2-2.60.7-2.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
Reopening the bug to follow the maintainer's suggestion since F31 glib2 is not avalable yet.
FEDORA-2019-9127055772 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-9127055772
Upgrading to Fedora 31 re-introduced this problem. Here are my package versions: glib2-2.62.2-1.fc31 anki-2.1.15-1.fc31 ibus-1.5.21-3.fc31
glib2-2.62.3-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-9127055772
glib2-2.62.3-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.
After upgrading to Fedora 32 the same problem (as described in my original comment https://bugzilla.redhat.com/show_bug.cgi?id=1762455#c0) reappears. Affected versions are: * anki-2.1.15-2.fc32 * telegram-desktop-2.0.1-1.fc32
I think it would be better actually to open a new bug.
(This seems to have already affected Beta AFAICT. Also I can't seem to get XIM working either under Qt.)
(In reply to Stefan Haan from comment #21) > After upgrading to Fedora 32 the same problem (as described in my original > comment https://bugzilla.redhat.com/show_bug.cgi?id=1762455#c0) reappears. > Affected versions are: > * anki-2.1.15-2.fc32 > * telegram-desktop-2.0.1-1.fc32 It's a different issue completely.
I filed a qt5-qtbase bug 1832086 for this now for F32.