On 2016-07-23 07:59, Alkis Georgopoulos wrote: > Gunnar, the live CD seeds are a different thing from package > dependencies.
I know that. The desktop file in the seed is reflected in the package dependencies, while the live file isn't. In the case of Lubuntu the fcitx stuff is included in the desktop file, which is why my command above works to show which packages they use. These are two possible approaches for MATE: 1. Include the needed packages (not only fcitx-bin) in the live seed, having them removed by Ubiquity at install as Aron mentioned for non- CJKV installs, and keep "auto" in im-config/gnome-language-selector. 2. Include the needed packages in the desktop seed instead as Lubuntu does, so they are also installed by Ubiquity, and change to "cjkv" in im-config/gnome-language-selector so fcitx isn't started/configured by default for non-CJKV users. With the latter approach the fcitx menu won't be shown in live sessions for non-CJKV users, which probably is good. > So if Martin wants fcitx to be there in the live CD, but not in the > installed system for those that don't need it, I think he can just > include the packages I mentioned in the seeds file. The reason why I showed which packages Lubuntu uses was that I think (not tested) that a couple of additional packages are needed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1605571 Title: apt install --no-install-recommends fcitx-bin, breaks dead keys Status in ubuntu-mate: New Status in im-config package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Bug description: Test case: remove everything related to fcitx. Then run: apt install --no-install-recommends fcitx-bin Then login with some locale that uses dead keys, for example the Greek locale. Then type e.g. ";"+"a". It's supposed to show "ά", but instead it shows "´α". At that point, fcitx isn't running, yet `im-config -a` reports that it's the selected input method. $ env | egrep '_IM|XMOD' CLUTTER_IM_MODULE=xim QT_IM_MODULE=xim XMODIFIERS=@im=fcitx QT4_IM_MODULE=xim GTK_IM_MODULE=xim If fcitx-bin is installed along with all its recommended dependencies, then fcitx is running normally and the issue described above doesn't occur anymore. At that point, the environment variables are: $ env | egrep '_IM|XMOD' CLUTTER_IM_MODULE=xim QT_IM_MODULE=fcitx XMODIFIERS=@im=fcitx QT4_IM_MODULE=fcitx GTK_IM_MODULE=fcitx At present I've only tested with the MATE desktop environment. It also happens with the MATE live CD, as fcitx-bin is indeed preinstalled there without its recommended dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1605571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
