← Back to team overview

desktop-packages team mailing list archive

[Bug 1430971] Re: Users not warned about switch to fcitx and no instructions are given


** Branch linked: lp:~attente/unity-control-center/1430971

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.

  Users not warned about switch to fcitx and no instructions are given

Status in indicator-keyboard package in Ubuntu:
Status in unity-control-center package in Ubuntu:
Status in unity-settings-daemon package in Ubuntu:

Bug description:
  Received the newest update to 0.0.0+15.04.20150310  a few minutes ago.
  There is a significant change to behavior with the change to fcitx
  from ibus.

  Users, however, are given no warning and no instructions on how to get
  their preferred input methods set up again.

  This has the potential to cause major inconveniences to users of non-
  English input methods, especially for Asian and other languages where
  the user needs a full IM and not just an alternative keyboard.

  1. Users need to be notified of the change and of the need install the
  necessary fcitx packages. Most users will need some instructions on
  what to do.

  2. After installing fcitx-libpinyin, the Input Method Configuration
  dialog still showed only keyboard layouts -- even after a reboot. I
  had to restart fcitx using the restart option in the drop-down menu
  before additional (non-keyboard) options showed up in the list.

  3. After that, finding pinyin input was still not intuitive. Past
  dialogs had you search for 'Chinese', then choose the appropriate
  method. In this case, however, 'Chinese' is only used in the 2nd
  (right) column, which is apparently not searched; so typing 'Chinese'
  led to no results. After removing the search term and scrolling to the
  bottom of the list, I saw that the IM's are listed by method name
  (Pinyin, BoPoMoFo, etc) and do not use the name of the language in the
  1st (left) column.  This is not expected by users and not consistent
  with the name of the keyboard methods.

To manage notifications about this bug go to: