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.
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