I presented the snap problem for James Henstridge, and he gave me a very useful hint: The Chromium snap makes use of the bionic library stack (the gnome-3-28-1804 snap) including the im module installed by fcitx- frontend-gtk3, i.e. the fcitx 4 gtk im module.
That made me think of <https://bugs.debian.org/977203>. That bug is still open, and as a result im-config currently sets these variables for fcitx 5: GTK_IM_MODULE=fcitx5 XMODIFIERS=@im=fcitx QT_IM_MODULE=fcitx5 It means that it explicitly looks for the fcitx 5 gtk im module, while Chromium only has access to the fcitx 4 one. So as a test I tweaked im-config to set: GTK_IM_MODULE=fcitx XMODIFIERS=@im=fcitx QT_IM_MODULE=fcitx and that made a difference. With that environment I could successfully input beautiful Chinese characters in Chromium using fcitx 5. :) Consequently there seems to be no need to add any extra stuff to apparmor to handle fcitx 5. Instead I see two options: 1. Change im-config's variable assignment, or 2. somehow add the fcitx 5 im modules for gtk and qt to the snap library stack. I'm going to consult with Debian's input method team about which route is preferable. @James: Do you see a problem from your POV with adding the fcitx 5 im modules to the snaps? ** Bug watch added: Debian Bug tracker #977203 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977203 ** Also affects: snappy Importance: Undecided Status: New ** Package changed: apparmor (Ubuntu) => im-config (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928360 Title: Switch to Fcitx 5 for Chinese To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
