https://bugs.kde.org/show_bug.cgi?id=422465
--- Comment #18 from Weng Xuetian <wen...@gmail.com> --- (In reply to Tyson Tan from comment #13) > I tested krita-5.0.0-prealpha-db8a16f-x86_64.appimage under Archlinux with > fcitx5, I was unable to use fcitx5 in that appimage. We often can't choose > which version of fcitx under Linux, it's either fcitx(4) OR fcitx5 for a > certain distro. I wonder if we need to package both fcitx-qt5 and fcitx5-qt > at the same time? No, for compatibility, both im module support fcitx4 / 5. Actually I just tested with https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/krita-5.0.0-prealpha-b55fcd5-x86_64.appimage Both fcitx4/5 works fine with this image on my system. Did you set QT_IM_MODULE=fcitx ? run it with QT_DEBUG_PLUGINS=1 should gives you QFactoryLoader::QFactoryLoader() looking at "/tmp/.mount_krita-43CzQH/usr/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin.so" Found metadata in lib /tmp/.mount_krita-43CzQH/usr/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin.so, metadata= { "IID": "org.qt-project.Qt.QPlatformInputContextFactoryInterface.5.1", "MetaData": { "Keys": [ "fcitx" ] }, "archreq": 0, "className": "QFcitxPlatformInputContextPlugin", "debug": false, "version": 330752 } Got keys from plugin meta data ("fcitx" -- You are receiving this mail because: You are watching all bug changes.
