Bug#1033097: im-config: Fcitx5 does not start automatically in KDE plasma Wayland
Control: reassign -1 im-config 0.55-1
Control: affects -1 fcitx5
Control: severity -1 important
Control: retitle -1 im-config: Fcitx5 does not start automatically in
KDE plasma Wayland
On 2023-03-17 10:27, Jun Nogata wrote:
Dear Maintainer,
Fcitx5 will not start in KDE Plasma Wayland.
When I go to KDE System Settings and open Regional Settings -> Input
Methods, I get the message "Cannot connect to Fcitx by DBus, is Fcitx
running?". If I press the "Run Fcitx" button here, Fcitx5 starts and
I can type Japanese.
In KDE Plasma X11, Fcitx5 is automatically started and Japanese can
be input.
Thanks for your report.
I made some tests with Kubuntu 23.04, and the problem seems to be with
the im-config file /etc/xdg/autostart/im-launch.desktop. I see this line
in the syslog:
2023-03-17T18:46:15.452477+01:00 gunnar-kubuntu-lunar-230317
systemd[865]:
/run/user/1000/systemd/generator.late/app-im\x2dlaunch@autostart.service:14:
Ignoring unknown escape sequences: "if [ "x\$XDG_SESSION_TYPE" =
"xwayland" ] ; then exec env IM_CONFIG_CHECK_ENV=1 im-launch true; fi"
How are those escapes added??
Anyway, it works for me in a wayland session if I drop the condition
from the Exec line in /etc/xdg/autostart/im-launch.desktop so it looks
like this:
Exec=sh -c 'exec env IM_CONFIG_CHECK_ENV=1 im-launch true'
But that's not what we want, is it? Suggestions for a proper way to
address this issue are most welcome.
--
Rgds,
Gunnar Hjalmarsson
Reply to: