Unable to install "Japanese (Anthy)" input source through the standard gnome-control-center means

After having installed everything you were prompted to, did you log out and log in again before checking if "Japanese (Anthy)" was available?

Yes I did, in fact I even rebooted, but still nothing.

It just struck me: Anthy is not the default IBus input method for Japanese in 16.04. Mozc is.

https://launchpad.net/ubuntu/+source/language-selector/0.156

So after having installed the Japanese language, logged out and logged in, it's the "Japanese (Mozc)" input source you should look for. Btw, I mentioned it here:

https://bugs.launchpad.net/ubuntu-gnome/+bug/1551283/comments/20

So on 16.04, if you prefer "Japanese (Anthy)", you need to install the ibus-anthy package manually.

Does that possibly explain it?

No, I already checked that an ibus-anthy was seemingly installed by the gnome-control-center, I just checked and it is installed, but it doesn't seem to be helping, also "Japanese (Mozc)" does not show as an input source either. Though I do have the "Mozc setup" installed (I did a search in the Activities Overview).

No, gnome-control-center in Ubuntu GNOME 16.04 does not install ibus-anthy. Can we please keep this discussion to only a *fresh* install of Ubuntu GNOME 16.04. Also, the GNOME packages which affect this are version 3.18 only, so your mentioning of 3.20 in the bug description is confusing.

I just tried it with a fresh install of Ubuntu GNOME, and could again successfully install Japanese, relogin, and select "Japanese (Mozc)".

Wondering if you misunderstand the Region & Language behavior, and interrupt the language install prematurely somehow. One way to find out could be that you take screenshots which show every single step you take, and attach them here.

I plan to upgrade to 16.04 tomorrow, but I will install a VM in the mean time to give you a screencast of what I am doing. But seriously, all I am doing is opening the region & language section, selecting Japanese, installing everything through the normal way and rebooting, then looking for Anthy I don't find an option but I do find ibus-anthy installed and I didn't install it.

I mentioned 3.20 because I was sure that I had tested all this on it too though I could be mistaken, but I thought I had.

On 2016-05-27 23:16, Nikita Yerenkov-Scott wrote:
> I plan to upgrade to 16.04 tomorrow, but I will install a VM in the
> mean time to give you a screencast of what I am doing.

Clean install is essential, whether in a VM or full install. Don't upgrade from e.g. 15.10.

> But seriously, all I am doing is opening the region & language
> section, selecting Japanese, installing everything through the normal
> way and rebooting,

That's what I do too.

> then looking for Anthy I don't find an option

Since Anthy should not be installed on 16.04?

> but I do find ibus-anthy installed and I didn't install it.

That's odd indeed. Unless you upgraded from 15.10 after all, and there are leftovers from it.

Looking forward to hear about your observations from a truly clean 16.04 install.

So was Anthy installed on 15.10 then? Because I didn't install it there either and it still got installed... This was on my 15.10 fresh install, not 16.04. I have a fresh install however of 16.04 in a VM and it appears as though everything runs as you described there and that the strange occurrences only occur on 15.10 which I no longer run. I will let you know though if Anthy magically installs itself though in my 16.04 VM.

Also, just out of interest, why was Mozc chosen to be the default to be installed for Japanese? I my experience Anthy is much easier to use and has many more features that it directly presents to you without too much configuration, if any. So why was Mozc chosen instead of it? What benefits does Mozc provide that Anthy doesn't?

Yes, up to 15.10 ibus-anthy was the default IBus IM for Japanese. As regards the reason for the change, you may want to talk with Ikuya (see bug #1547845) or some other Japanese user.

Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 16.04 (xenial) reached end-of-life in April 2019.

https://ubuntugnome.org/ubuntu-gnome-16-04-lts-is-here/
https://wiki.ubuntu.com/XenialXerus/ReleaseNotes/UbuntuGNOME

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.