Comment 25 for bug 1720250

On Wed, Oct 04, 2017 at 12:40:03AM -0000, Gunnar Hjalmarsson wrote:
> As Iain suggested on IRC
>
> https://irclogs.ubuntu.com/2017/10/03/%23ubuntu-devel.html#t15:52
>
> I checked out what the processes looked like for the two attempts at a
> solution, and attached a couple of files with my observations.
>
> Well, not sure what I should look for, to be honest, but that exercise
> inspired me to a possible solution: Since gdm3 always starts ibus-daemon
> anyway, I added a condition to /usr/share/im-config/data/21_ibus.rc so
> im-config does not start ibus-daemon if gdm3 is the DM. That seems to
> fix it.
>
> So I have uploaded yet another variant to the PPA.
>
> https://launchpad.net/~gunnarhj/+archive/ubuntu/im-config

Thanks Gunnar, good find.

I wonder what this is telling us - you end up with multiple copies of
iBus running or something? Or the order matters and somehow the
basic.target one starts up early enough and the other one doesn't?

From looking at that 21_ibus.rc script, it doesn't look like it's
crucial that im-config is the thing to actually execute iBus, right? If
that's the case, this is probably good. If it tests out, feel free to
upload.

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]