Comment 24 for bug 1928360

So it was changed in im-config. In Debian the change was uploaded to experimental instead of unstable/bullseye for now, since the principal fcitx package maintainer Shengjing Zhu senses some degree of uncertainty. He wants to give the users some time to provide feedback before changing it in bullseye (Debian 11).

@handsome_feng: Since Kylin will ship both fcitx 4 and fcitx 5 in 21.10, I'm thinking that Kylin would be a perfect platform for testing this input configuration. So it would be good if you could include some testing also of fcitx 5 and be attentive to possible issues in light of the fact that it loads the fcitx 4 im modules instead of the fcitx 5 ones.

@James: Leaving the just mentioned uncertainty aside, we can conclude that there seems to be no need to make any changes to the core18 based platform snaps. An upstream change was made in fcitx5 5.0.5 with the explicit purpose to deal with e.g. snaps where only fcitx 4 im modules are present; see <https://bugs.debian.org/977203#34>.

But it would be good if we somehow could test to confirm that fcitx 5 works with a core20 based platform snap without modifying the apparmor abstractions for fcitx.