Comment 4 for bug 1430971

I've already removed all fcitx packages except fcitx-data, libfcitx-config4, libfcitx-glient0, libfcitx-utils0 (all required by Unity Control Center, as you know) and reset the system IM back to Ibus; so I'm back to normal.

I didn't really question the fcitx packages in the upgrade since it's now supported and it seemed reasonable to have it readily available.

I assumed the bug was with indicator-keyboard because that's where problem showed itself in a big way, but based on your earlier comment I wonder if the bug isn't in unity-settings-daemon and how the current IM is detected.

I have a third laptop that I had not yet upgraded. This time I added in ibus-libpinyin IM *before* doing the upgrade. This time fcitx was added to the startup programs and set itself in update-alternatives for xinput.d, but it did not replace Ibus as the system-wide IM in Language Support as it had before. The topbar had both indicators. When I switched the system-wide IM to fcitx and then set it back to Ibus (restarting each time), the ibus-libpinyin IM had been removed from Text Entry.

So apart from the question of the fcitx packages showing up in the upgrade, it seems like various config scripts are not correctly detecting Ibus.

If I can do any additional debugging, please let me know.