Control: severity -1 serious Control: affects -1 src:tasksel On Thu, Oct 03, 2019 at 05:49:37AM -0400, Jeremy Bicha wrote: > On Wed, Oct 2, 2019 at 9:51 PM Mo Zhou <lu...@debian.org> wrote: > > I've been using fcitx as the default Chinese input method for decades. > > Recommending ibus simply breaks everything for me. > > GNOME Shell uses Wayland by default. It is my understanding that ibus > works in GNOME's Wayland session but fcitx does not. > > Have you tried using im-config to choose fcitx over ibus? If that does > not work, maybe you should file an im-config bug instead? >
Sorry I just find this bug when I read another bug[1] which is recently reported to the debian-input-method team. It has been working well previously that the choice of input method is decided by src:tasksel package. Please see all the all the task-*-desktop packages: + fcitx is recommended by task-telugu-desktop, task-malayalam-desktop, task-kannada-desktop, task-chinese-t-desktop, task-chinese-s-desktop, task-amharic-desktop. + uim is recommended by task-japanese-desktop. + ibus is recommended by task-tamil-gnome-desktop, task-korean-desktop Now GNOME just takes over the responsibility. Please don't, it't just broken without coordination of src:tasksel maintainer. + Users are now possible to install two input engines. It troubles than benefits. + And the tasksel won't install corresponding language library for ibus. + And for the im-config, it's not possible to decide which engine is preferred by the tasksel data. Yes you can say that users change it by hand, but it's not what we want to achieve. We want a working desktop for different users by default. If GNOME maintainer want to change the default input method, it's better to do it in tasksel package. Please downgrade ibus to Suggests for bullseye. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983695
signature.asc
Description: PGP signature
