Bug#714914: fcitx started while no env are set with gdm 3.8

2013-07-14 Thread Osamu Aoki
Control: tag 714914 + unreproducible Hi, This GNOME 3.8 does many funky thing overriding ENVIRONMENT etc. I was not surprised. This is their design decision to override old fashioned configuration under some condition. (I suspect if they see no IM running, they start IM.) With current design,

Bug#714914: fcitx started while no env are set with gdm 3.8

2013-07-14 Thread Aron Xu
On Mon, Jul 15, 2013 at 12:25 AM, Osamu Aoki os...@debian.org wrote: $ set |grep IM_MODULE;set |grep XMODIFIERS CLUTTER_IM_MODULE=xim GTK_IM_MODULE=ibus QT4_IM_MODULE=ibus XMODIFIERS=@im=ibus So it has right values and im-config/ibus of this version is working. I haven't tried myself, but

Bug#714914: fcitx started while no env are set with gdm 3.8

2013-07-04 Thread YunQiang Su
Package: im-config After upgrade to gdm 3.8, fctix can start while it cannot input anymore, As it seems that neither GTK_IM_MODULE nor QT4_IM_MODULES are set. -- YunQiang Su -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#714914: fcitx started while no env are set with gdm 3.8

2013-07-04 Thread Osamu Aoki
On Thu, Jul 04, 2013 at 04:42:09PM +0800, YunQiang Su wrote: Package: im-config After upgrade to gdm 3.8, fctix can start while it cannot input anymore, As it seems that neither GTK_IM_MODULE nor QT4_IM_MODULES are set. This is what I was afraid. Finally Let me upgrade and figure out