Bug#645353: marked as done (scim-bridge-client-gtk: After upgrade GTK no longer detects scim-bridge input method)
Your message dated Mon, 05 Mar 2012 09:29:11 +0000
with message-id <E1S4UEB-0002aC-R0@franck.debian.org>
and subject line Bug#642371: Removed package(s) from unstable
has caused the Debian Bug report #645353,
regarding scim-bridge-client-gtk: After upgrade GTK no longer detects scim-bridge input method
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact firstname.lastname@example.org
Debian Bug Tracking System
Contact email@example.com with problems
--- Begin Message ---
On my computer I configured SCIM about two years ago and it worked without
problems up to now. But since the last upgrade SCIM stopped working for GTK
applications (such as
iceweasel or libereoffice).
I must admit, that I don't know the proper way to configure SCIM under Debian.
And maybe the way I did it two years ago is no longer appropriate. In case that
my non-standard way of configuring SCIM causes the problems I am sorry for the
noise. However, the upgrade broke SCIM for me, so this might also be of
interest for others.
The thing is, that after upgrading "scim-bridge-client-gtk" to version
0.4.16-3, the file "im-scim-bridge.so" moved from
"/usr/lib/gtk-2.0/2.10.0/immodules/im-scim-bridge.so" to "/usr/lib/i386-linux-
On my system, the environment variable $GTK_IM_MODULE is set during the start
the X-session by the script "/etc/X11/Xsession.d/80im-switch". That script
eventually sources "/etc/X11/xinit/xinput.d/all_ALL" which is a symbolic link
$GTK_IM_MODULE is set there as following:
if [ -e /usr/lib/gtk-2.0/*/immodules/im-scim-bridge.so ]; then
elif [ -e /usr/lib/gtk-2.0/*/immodules/im-scim.so ]; then
After the upgrade, im-scim-brigde.so was no longer found and the environment
variable $GTK_IM_MODULE was set to "xim".
Also "gtk-query-immodules-2.0" was unable to detect the module.
As workaround, I added a symbolic link from the new location to
"/usr/lib/gtk-2.0/2.10.0/immodules". Then "gtk-query-immodules-2.0" was again
able to detect scim-bridge as input method. I also updated
"/usr/lib/gtk-2.0/2.10.0/gtk.immodules" with the output of "gtk-query-
It works for me now, but I wonder what would be the proper way to configure
SCIM for GTK after the upgrade.
Oh, and I guess the same applies to the package "scim-gtk2-immodule" which
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 220.127.116.11 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages scim-bridge-client-gtk depends on:
ii libatk1.0-0 2.2.0-1
ii libc6 2.13-21
ii libcairo2 1.10.2-6.1
ii libfontconfig1 2.8.0-3
ii libfreetype6 2.4.6-2
ii libgdk-pixbuf2.0-0 2.24.0-1
ii libglib2.0-0 2.28.6-1
ii libgtk2.0-0 2.24.4-3
ii libpango1.0-0 1.28.4-3
ii libx11-6 2:1.4.4-2
ii scim-bridge-agent 0.4.16-3
scim-bridge-client-gtk recommends no packages.
scim-bridge-client-gtk suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: firstname.lastname@example.org,email@example.com,firstname.lastname@example.org,email@example.com,firstname.lastname@example.org,email@example.com,firstname.lastname@example.org,email@example.com,firstname.lastname@example.org,email@example.com,firstname.lastname@example.org,email@example.com,
- Cc: firstname.lastname@example.org, email@example.com
- Subject: Bug#642371: Removed package(s) from unstable
- From: Debian FTP Masters <firstname.lastname@example.org>
- Date: Mon, 05 Mar 2012 09:29:11 +0000
- Message-id: <E1S4UEB-0002aC-R0@franck.debian.org>
as the package scim-bridge has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see http://bugs.debian.org/642371
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
Debian distribution maintenance software
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)
--- End Message ---