Bug#977203: IM_MODULE env for fcitx5 should be "fcitx"
On Sat, Jun 05, 2021 at 11:58:14PM +0200, Gunnar Hjalmarsson wrote:
> On 2021-06-05 22:51, Shengjing Zhu wrote:
> > Situation has changed since fcitx5 5.0.4, which includes a compatible
> > frontend for fcitx4 module.
> > https://salsa.debian.org/input-method-team/fcitx5/-/commit/7780c8f7f9bcde2fcff6ae7fc3ce5ab2c40ebe63
> >
> > The origin purpose is to support property software which only ships
> > with fctix4 modules, as well as snap, flatpak, etc, which can't use
> > the system library.
>
> Ah, so that's why my trivial Chromium snap test worked with
> GTK_IM_MODULE=fcitx. :)
>
> What's the conclusion then as regards this bug? Is it time to change to
> "fcitx" in im-config in unstable (and somehow also in bullseye) without
> worrying about users who have both fcitx 4 and fcitx 5 installed?
>
We eventually need to align with upstream for the IM_MODULE env. But I'm not
sure what should be done before bullseye release.
Reply to: