Users not warned about switch to fcitx and no instructions are given
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-keyboard (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
unity-control-center (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
unity-settings-daemon (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Received the newest update to 0.0.0+15.
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.
Related branches
- Sebastien Bacher: Approve
-
Diff: 81 lines (+23/-13)2 files modifieddebian/control (+1/-2)
panels/region/gnome-region-panel-input.c (+22/-11)
- Sebastien Bacher: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 80 lines (+31/-28)2 files modifieddebian/control (+1/-2)
plugins/keyboard/gsd-keyboard-manager.c (+30/-26)
Changed in unity-control-center (Ubuntu): | |
status: | New → Confirmed |
Changed in unity-settings-daemon (Ubuntu): | |
status: | New → Confirmed |
Changed in unity-control-center (Ubuntu): | |
importance: | Undecided → High |
Changed in indicator-keyboard (Ubuntu): | |
importance: | Undecided → High |
Changed in unity-settings-daemon (Ubuntu): | |
importance: | Undecided → High |
Changed in indicator-keyboard (Ubuntu): | |
status: | Confirmed → Invalid |
> There is a significant change to behavior with the change to fcitx from ibus.
Hi, could you please elaborate on what happened with your update? That update doesn't switch your selected input method framework from ibus to fcitx. Also, the update should have been an effective no-op if Fcitx wasn't already installed in the first place...