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 [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720250 Title: im-config configuration ignored with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
