Arch Linux User Repository

https://gitlab.manjaro.org/packages/extra/manjaro-asian-input-support/

Prefer ClassicUI in the KDE Wayland environment.

Only in KDE Plasma (Wayland) environment, the setting has been changed.

Following updates to QT and Mozc, the input position does not change from application to application and is displayed in the top left-hand corner. Therefore, change the setting to use classicui instead of WaylandUI as standard.

Fcitx5 displays a warning message in the Wayland environment because GTK_IM_MODULE and QT_IM_MODULE are set, but please do not worry about it and use it as it is. If you want to change the text or background colour, change the theme to something like plasma in Fcitx5's classicui settings, and also change the Follow light-dark theme setting in the system settings to ON.

Okay, I get what you mean.

@willvar

The version and release number have not been changed as there are no functional changes.
I would appreciate it if you could reinstall the software and downgrade the version number or uninstall and re-install.

Oh I see your commit but the .SRCINFO is not updated so I didn't get any update.

@willvar
As you say, it would certainly be annoying.
I have now fixed the version.

Since the AUR is built by the users themselves, it would be more appropriate to fix the version rather than leave the upstream settings. Your point is well taken.

Thank you for your report.

Here I am again, with a question about the following PKGBUILD snippet:

pkgver() {
    date +%Y%m%d
}

I’ve noticed that when I install fcitx5-input-support, the package version always matches the current date. However, during rolling updates, I often see messages like:

:: Searching databases for updates...
-> fcitx5-input-support: local (20250403-1) is newer than AUR (20250211-1)

The local version is always flagged as newer than the AUR version, this is a little bit annoying. Could you kindly clarify this? I’m curious about the reason behind it, thanks!

@MatrixC7

Fcitx5 has been updated and the problems I encountered earlier, caused by setting environment variables, may have improved. Nevertheless, the fact remains that Fcitx5 displays a message at startup in the KDE+Wayland environment, prompting the user to remove GTK_IM_MODULE and QT_IM_MODULE. You should therefore exchange your views with the developers and maintainers of Fcitx5 itself. If you think that my stance of following it is wrong, then you should create your own package and undertake to include support for those who use your package. That would be a practical solution.

It is not constructive to ignore my previous posts, specifically the cases where I have encountered trouble with setting environment variables, and to keep pointing out one-sidedly that my choices are wrong without also telling me what environment you are using. This is because even if You didn't encounter any problems in your environment, it is a fact that I did in my old environment.

As stated in the Fcitx5 startup message, it is recommended to use the Kwin VitrualKeyboard to start the Fcitx5 Wayland Launcher. That would still be the message from the developers. If you disagree with it, you should tell the Fcitx5 developers and maintainers.

You are asking me to do something different from the configuration recommended by the Fcitx5 developers, and I don't think it is a good decision for me to take you at your word. Therefore, I recommend that you create your own package and maintain it yourself. By doing so, the AUR can fulfil the purpose for which it exists.