Problems with Fcitx

Support
1

Hello,

  • OpenMandriva Lx version: ROME after latest distro sync

  • Desktop environment (KDE, LXQT…): default Plasma after distro sync

  • Description of the issue (screenshots if relevant):
    Please keep in mind this problem is not unique to the latest release.
    I was not able to make Fcitx4 work in the previous release for ROME, but now we have 5 I thought I’d be lucky.
    The problem is different now, however.
    In the previous release kcm would install but not work.
    In the current release kcm and Fcitx5 seem broken.

I also have this other problem with the Flatpak for Fcitx5 where it works well, but it only works within Flatpak apps and not the whole system.
Fixing either will work for me

  • Relevant informations (hardware involved, software version, logs or output…):
package kcm-fcitx-0.5.5-1.x86_64 from @System requires libfcitx-config.so.4()(64bit), but none of the providers can be installed
  - package kcm-fcitx-0.5.5-1.x86_64 from @System requires libfcitx-core.so.0()(64bit), but none of the providers can be installed
  - package kcm-fcitx-0.5.5-1.x86_64 from @System requires libfcitx-utils.so.0()(64bit), but none of the providers can be installed
  - package fcitx5-5.1.12-1.x86_64 from rolling-x86_64 obsoletes fcitx < 5 provided by fcitx-4.2.9.6-2.x86_64 from @System
  - package fcitx5-5.1.12-1.x86_64 from rolling-x86_64 obsoletes fcitx < 5 provided by fcitx-4.2.9.6-2.x86_64 from rolling-x86_64
  - cannot install the best update candidate for package kcm-fcitx-0.5.5-1.x86_64
  - cannot install the best update candidate for package fcitx-4.2.9.6-2.x86_64

problem with installed package fcitx5-5.1.12-1.x86_64

  - installed package fcitx5-5.1.12-1.x86_64 obsoletes fcitx < 5 provided by fcitx-4.2.9.6-2.x86_64 from rolling-x86_64
  - package fcitx5-5.1.12-1.x86_64 from rolling-x86_64 obsoletes fcitx < 5 provided by fcitx-4.2.9.6-2.x86_64 from rolling-x86_64
  - package kcm-fcitx-0.5.5-1.x86_64 from rolling-x86_64 requires libfcitx-utils.so.0()(64bit), but none of the providers can be installed
  - package kcm-fcitx-0.5.5-1.x86_64 from rolling-x86_64 requires libfcitx-config.so.4()(64bit), but none of the providers can be installed
  - package kcm-fcitx-0.5.5-1.x86_64 from rolling-x86_64 requires libfcitx-core.so.0()(64bit), but none of the providers can be installed
  - conflicting requests
2

It will probably need to be rebuilt with the UM to ROME happening.

3

It appears they never ported that to Qt6/KF6. I will see if that is something I can get done.

1 Like
4

It looks like kcm-fcitx has been abandoned. @bero has suggested obsoleting it with fcitx5-qt. It is building in ABF now with those changes for cooker. If you are able to test it, that would be great.

5

If you tell me exactly what to do then I can test it.

6

Install fcitx5-qt on a cooker install.

7

When testing the Wayland session it gave me this message with the package installed:

“Fcitx should be launched by KWin under KDE Wayland in order to use Wayland input method frontend. This can improve the experience when using Fcitx on Wayland. To configure this, you need to go to “System Settings” → “Virtual keyboard” and select “Fcitx 5” from it. You may also need to disable tools that launches input method, such as imsettings on Fedora, or im-config on Debian/Ubuntu. For more details see Using Fcitx 5 on Wayland - Fcitx”

I would assume a similar input type would be available in the X11 session.