Thanks, Mitsuya, for valuable input! As regards the upstart stuff, it was introduced before Unity8, and since I don't know if all the flavors have switched to systemd for user session, I'm disinclined to drop it at this time.
I uploaded a test version of im-config here: https://launchpad.net/~gunnarhj/+archive/ubuntu/im-config The difference compared to the version in the queue is that I made use of your im-config.service script and changed the related symlink accordingly. Even if the variables seem to be properly set, I made this observation: $ systemctl --user list-unit-files | grep im-config im-config.service disabled Can't tell if that is of any significance. Anyway, I'll try to make some experienced developer review this solution. It looks promising to me. -- 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
