https://bugs.kde.org/show_bug.cgi?id=485494

Weng Xuetian <wen...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Packages User Edition       |Packages Testing Edition
                 CC|                            |wen...@gmail.com
           Assignee|neon-b...@kde.org           |carlosdema...@gmail.com

--- Comment #6 from Weng Xuetian <wen...@gmail.com> ---
Fcitx dev here, I downloaded
https://files.kde.org/neon/images/testing/20240423-0253/neon-testing-20240423-0253.iso
and installed it in qemu. 

So indeed, any program that loads fcitx5's im module would crash immediately.
But with my experience on archlinux, it should be fine with either Qt6.6 or Qt
6.7.

So I just try this on kwrite, QT_DEBUG_PLUGINS=1 QT_IM_MODULE=fcitx kwrite
And it shows following lines:
```
{
    "IID": "org.qt-project.Qt.QPlatformInputContextFactoryInterface.5.1",
    "MetaData": {
        "Keys": [
            "fcitx",
            "fcitx5"
        ]
    },
    "archlevel": 1,
    "className": "QFcitx5PlatformInputContextPlugin",
    "debug": false,
    "version": 394752
}
```
Comparing to other plugins, they are showing "395008".
394752 is 0x60600, and 395008 is 0x60700, which is the Qt version
(major<<16|minor<<8|patch).

It clearly indicates that the qt6 part with in fcitx5-qt is built against Qt
6.6, not the Qt 6.7. For qpa platform plugin it's unfortunate that it need to
be rebuilt against any Qt minor update.

I also tried to rebuild with neon's deb source. Problem also go away, so it
seems that a rebuild should fix the issue.

For users who hit this issue but still want to use fcitx5, if you ARE planning
using wayland, you can:
1. Go to TTY (Ctrl+Alt+F(1,2,3...)
2. Run "im-config -n none", this will disable im-config profile and all the
environment variable like QT_IM_MODULE to be set. This is actually OK if you're
gonna use wayland.
3. Now you should be able to login, you can go to Systemsettings->Virtual
keyboard-> select fcitx5 there. You should be able to use fcitx5 input method
as long as application is running under wayland. 

For more details on other thing to setup, check
https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland#KDE_Plasma

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to