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, im-config can not do much. But read on to find out why unreproducible ... and how to address this type of problems. 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. How to tame GNOME3 IM environment deserves attention and wishlist feature request. Basically 2 approaches: extend im-config to support some desktop file (or its follow-up) type interface or other for GNOME3. (short term solution) Let's discuss this at http://bugs.debian.org/654307 replace im-config with im-chooser (FEDORA) like system which can dynamically set IM environment. (long term solution) Let's discuss this at http://bugs.debian.org/716898 As to this unreproducible bug, please check this problem again with the newer gnome-shell. It may be solved by now. It is not reproducible here. $ apt-cache policy fcitx ibus im-config gnome-shell gdm3 fcitx: Installed: 1:4.2.7-2 Candidate: 1:4.2.7-2 Version table: *** 1:4.2.7-2 0 500 http://ftp.jp.debian.org/debian/ jessie/main amd64 Packages 500 http://ftp.jp.debian.org/debian/ sid/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.4.1-7 0 500 http://ftp.jp.debian.org/debian/ wheezy/main amd64 Packages ibus: Installed: 1.5.1.is.1.4.2-3 Candidate: 1.5.1.is.1.4.2-3 Version table: 1.5.2-4 0 100 http://ftp.jp.debian.org/debian/ experimental/main amd64 Packages *** 1.5.1.is.1.4.2-3 0 500 http://ftp.jp.debian.org/debian/ sid/main amd64 Packages 100 /var/lib/dpkg/status 1.5.1.is.1.4.2-2 0 500 http://ftp.jp.debian.org/debian/ jessie/main amd64 Packages 1.4.1-9 0 500 http://ftp.jp.debian.org/debian/ wheezy/main amd64 Packages im-config: Installed: 0.22-3 Candidate: 0.22-3 Version table: *** 0.22-3 0 500 http://ftp.jp.debian.org/debian/ jessie/main amd64 Packages 500 http://ftp.jp.debian.org/debian/ sid/main amd64 Packages 100 /var/lib/dpkg/status 0.21 0 500 http://ftp.jp.debian.org/debian/ wheezy/main amd64 Packages gnome-shell: Installed: 3.8.3-1 Candidate: 3.8.3-1 Version table: *** 3.8.3-1 0 100 http://ftp.jp.debian.org/debian/ experimental/main amd64 Packages 100 /var/lib/dpkg/status 3.4.2-11 0 500 http://ftp.jp.debian.org/debian/ jessie/main amd64 Packages 500 http://ftp.jp.debian.org/debian/ sid/main amd64 Packages 3.4.2-7 0 500 http://ftp.jp.debian.org/debian/ wheezy/main amd64 Packages $ 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. If you agree my assessment, let's close this to keep BTS clean. Regards, Osamu PS: When I was playing with experimental and installed currently broken ibus 1.5.2-4 (experimental) with GNOME 3.8?, system failed to start ibus but started fcitx. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
