Looking at Plucky where the bug doesn't occur, it seems like it should
have been happening there too. ibus-mozc-gnome-initial-setup.sh is run
and it does write out ibus-mozc-gnome-initial-setup-done. But it fails
to write the dconf changes for some reason. When run manually, it
succeeds and the bug can be made to appear in Plucky. So it seems like a
race condition prevented the unwanted dconf write from bothering the
live session in Plucky. Indeed I have also seen machines where it didn't
happen in Questing either.
Mozc isn't the only input method and Japanese isn't the only language
available in live sessions, it should be there. Just that mozc seems to
be the only one with an overly assertive installation script.
Unfortunately, because "org.gnome.desktop.input-sources current uint32
0" is deprecated and ignored, the script is allowed to edit the list of
"org.gnome.desktop.input-sources sources" and not expect the shell to
instantly change to the new input source. So in that respect, this is
starting to look like a shell bug again for changing input sources as
soon as a new one is installed.
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2123846
Title:
Input method indicator defaults to Japanese in live sessions
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2123846/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
