Ok, the reason I left a comment here was very logical: disabling the code in /etc/profile.d/input-method-config.sh script made the problem "go away". And in the header of this script there is a reference to this particular bug number, so that was my first place to go to.
However, I completely agree with you, that the real cause of the problem may be elsewhere and it should be reported against the corresponding subsystem. I will do as you suggest as soon as I have more information (I am not working on this actively, as my "workaround" seems to be ok, but of course I am curious and so "in the back of my mind" I am still considering this issue :) -- 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: Invalid Status in im-config package in Ubuntu: Fix Released 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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp