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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1720250 Title: im-config configuration ignored with gdm3 Status in gdm3 package in Ubuntu: Confirmed Status in im-config package in Ubuntu: Confirmed Bug description: After having logged in via gdm3, the IM related environment variables are always set like this: $ env | grep -E '_IM|XMOD' QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Changing ~/.xinputrc to e.g. xim makes no difference, so gdm3 prevents all other IM frameworks but IBus from working. This problem seems to be similar to bug #1594681 (which was fixed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
