Input method isn't working in yakkety

[t4eg]

After booting my PC, I can't switch fcitx-mozc input method. (Japanese <-> English)
Keyboard icon also disappear in the tasktray.

Changing "Language support - Language" and re-login will solve the problem but this is very annoying.

Ubuntu 16.10 yakkety.
previous environment: Ubuntu 16.04LTS was working well.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[eric-1111 (eric-1111)]

Same problem here. fcitx fails to load when first log in to Ubuntu desktop. Workarounds: Log out then log back in works. Or manually start fcitx.

It looks like fcitx crashed when first loaded:
[code]
Oct 20 13:23:57 uc systemd[1410]: Started Unity Settings Daemon.
Oct 20 13:23:57 uc sh[1783]: dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge:unity-gtk-module
Oct 20 13:23:57 uc systemd[1410]: Started Unity GTK Module Environment variables.
Oct 20 13:23:57 uc systemd[1410]: Starting Unity Shell v7...
Oct 20 13:23:57 uc systemd[1410]: Started GNOME Session Manager.
Oct 20 13:23:57 uc sh[1801]: + [ ubuntu != gnome-classic ]
Oct 20 13:23:57 uc sh[1801]: + export GNOME_SESSION_XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
Oct 20 13:23:57 uc sh[1801]: + [ ubuntu = gnome-flashback-metacity ]
Oct 20 13:23:57 uc sh[1801]: + exec gnome-session --session=ubuntu
Oct 20 13:23:57 uc systemd[1410]: Started Launch and configure input method.
Oct 20 13:23:58 uc sh[1782]: =========================
Oct 20 13:23:58 uc sh[1782]: FCITX 4.2.9.1 -- Get Signal No.: 15
Oct 20 13:23:58 uc sh[1782]: Date: try "date -d @1476984238" if you are using GNU date ***
Oct 20 13:23:58 uc sh[1782]: ProcessID: 1867
Oct 20 13:23:58 uc sh[1782]: /usr/bin/fcitx(+0x14d6)[0x55b84d6d84d6]
Oct 20 13:23:58 uc sh[1782]: /lib/x86_64-linux-gnu/libc.so.6(+0x35860)[0x7fb618162860]
Oct 20 13:23:58 uc sh[1782]: /lib/x86_64-linux-gnu/libc.so.6(__read+0x10)[0x7fb618224c70]
Oct 20 13:23:58 uc sh[1782]: /lib/x86_64-linux-gnu/libc.so.6(_IO_file_underflow+0x140)[0x7fb6181a96b0]
Oct 20 13:23:58 uc sh[1782]: /lib/x86_64-linux-gnu/libc.so.6(getdelim+0x288)[0x7fb61819cdc8]
Oct 20 13:23:58 uc sh[1782]: /usr/lib/x86_64-linux-gnu/libfcitx-config.so.4(FcitxConfigParseIniFp+0x89)[0x7fb61892c479]
Oct 20 13:23:58 uc sh[1782]: /usr/lib/x86_64-linux-gnu/libfcitx-config.so.4(FcitxConfigParseConfigFileDescFp+0x2a)[0x7fb61892e53a]
Oct 20 13:23:58 uc sh[1782]: /usr/lib/x86_64-linux-gnu/libfcitx-core.so.0(FcitxGlobalConfigLoad+0x160)[0x7fb618b47da0]
Oct 20 13:23:58 uc sh[1782]: /usr/lib/x86_64-linux-gnu/libfcitx-core.so.0(+0x8391)[0x7fb618b45391]
Oct 20 13:23:58 uc sh[1782]: /usr/lib/x86_64-linux-gnu/libfcitx-core.so.0(FcitxInstanceRun+0x210)[0x7fb618b460b0]
Oct 20 13:23:58 uc sh[1782]: /usr/bin/fcitx(+0xfbc)[0x55b84d6d7fbc]
Oct 20 13:23:58 uc sh[1782]: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fb61814d3f1]
Oct 20 13:23:58 uc sh[1782]: /usr/bin/fcitx(_start+0x2a)[0x55b84d6d803a]
Oct 20 13:23:58 uc dbus-daemon[1432]: Successfully activated service 'org.ayatana.bamf'
Oct 20 13:23:58 uc systemd[1410]: Started BAMF Application Matcher Framework.
[/code]

[eric-1111 (eric-1111)]

.config/fcitx/log/crash.log:
fcitx: BadWindow (invalid Window parameter)

[t4eg (t4eg)]

This bug seems like fixed now.

[t4eg (t4eg)]

Oops, I judged prematurely.
The problem is still there :(

[t4eg (t4eg)]

I updated from 16.10 to 17.04.
This problem disappeared on Ubuntu 17.04.