Hello Gunnar: For your comment #72: For SRU justification, think it in this way: This bug is a serious regression compare to Ubuntu releases in pre-Unity era. And its effect is blocking. How can we leave it semi-fixed for three releases including an LTS has 5 year life time?
The of principle im-config or backported im-switch is the following: /usr/bin/im-launch does two things: 1. Start IM 2. exec $@ (Execute whatever its argument specifies) /etc/X11/Xsession.d/70im-config_launch or 70im-switch_launch does one thing: STARTUP="/usr/bin/im-launch $STARTUP" (alter STARTUP variable) In contract, in origin im-switch, /etc/X11/Xsession.d/80im-switch directly start IM. What's the magic of STARTUP variable? You may issue the following command first: grep STARTUP /etc/X11/Xsession.d/* Then you will notice that in several files do something like this: STARTUP="some_command $STARTUP" And in /etc/X11/Xsession.d/99x11-common_start, it simply exec $STARTUP If all the some_command follows the convention that it does its own job then exec its argument, a reverse sequential order of execution is archived. That's why im-config or backported im-switch use 70 instead of 80. Because dbus-launch uses 75, alter STARTUP variable in 70 can guarantee that IM is started after DBus, which is desired. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875435 Title: iBus indicator does not show on the panel To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/875435/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
