On Fri, Aug 2, 2013 at 11:35 PM, Osamu Aoki <os...@debian.org> wrote: > Hi, > > On Wed, Jul 31, 2013 at 09:34:08PM +0800, Aron Xu wrote: >> On Wed, Jul 31, 2013 at 1:23 AM, Toni Mueller <supp...@oeko.net> wrote: >> > On Tue, Jul 30, 2013 at 05:00:09PM +0000, Debian Bug Tracking System wrote: >> >> This is not a bug, you should use im-config to set proper env. >> >> include GTK_IM_MODULES, QT4_IM_MODULES etc >> > >> > I actually do this. I lose the ability to use fcitx in certain programs >> > in the middle of a session, at random points. Like I work for, say, an >> > hour, and suddenly, the ability to use fcitx with certain (console) >> > programs goes away in the middle of said session. >> > >> >> This is a bug in im-config, because im-config now launch input method >> after dbus is successfully initialized. > > Yes. (we are talking wheezy/jessie) > >> But there is problem that it >> exports those environmental variables at that time, so that > > No. It exports them before launching dbus. > > This is enabled via $IM_CONFIG_PHASE variable in the defualt > configuration. >
$ps aux | grep im-launch | grep -v grep aron 1462 0.0 0.0 24328 860 ? S 18:37 0:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/im-launch /usr/bin/startkde So the command line is: /usr/bin/dbus-launch --exit-with-session /usr/bin/im-launch /usr/bin/startkde And this means im-launch is executed by dbus-launch, so that the dbus session is active before im-launch gets executed. This has the effect that other direct child process of this dbus-launch process does not have relevant variables set. Regards, Aron Xu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org