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 <[email protected]> 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. > applications that have components spawned directly by the desktop > dbus-daemon process will not have those environmental variables set. Wrong. Anyway, Toni is using extremely convoluted script from .bashrc. That is too late to set up im-config and should not work. "im-config -n" should be run before /etc/X11/Xsession.d/70im-config_launch X start up script if it is used in the way he uses. Osamu -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
