Hi forks,
I thank Gunnar for his good work on this package. I am almost done with 0.59.
I will close this bug with the 0.59 upload.
As I tested now on forky-testing, KDE worked very well without im-config now.
This may be due to input method support at wayland level got improved in last 3
years.
* KDE Plasma DE (Wayland)
Install one of the followings:
* ibus framework: ibus-<your_input_method_engine_name> package
* fcitx5 framework: fcitx5-<your_input_method_engine_name> package
* fcitx5 framework offers ibus-compatible API
Select an input method framework as the virtual keyboard
The im-config code got very convoluted because I did it with motivation to
minimize line changes under release freeze and it kept growing.
I took this opportunity to refactor it and remove all re-entry, so I can
understand how this works again after 6 years.
This also clarifies, im-config will not be required for Wayland environment
(updated package description).
Here is a note in README.Debian of 0.59.
----------
NOTE:
Under the good old X11 DE system, we could rely on /etc/X11/Xsession.d/
to initialize the IM framework. Automation of this is the original
and current scope of this im-config package.
Under the wayland DE system, there is no single established common hook
script location. Initially for GNOME, attempts to configure it from
im-config was made using /etc/profile.d/* . But GNOME doesn't need any
help from im-config. Also as I tested, KDE doesn't use /etc/profile.d/*
nor /etc/environment.d/* . So no stable method to set up environment
variables for KDE.
Thus I decided to disable all im-config actions under Wayland.
-----------
Technical details are documented in debian/README.internal in the source tree.
https://salsa.debian.org/input-method-team/im-config/-/merge_requests/20
Let me polish details ....
Osamu
