Apparently, gtk+ ebuilds are now always using CHOST-based directory for gtk.immodules: GTK2_CONFDIR="/etc/gtk-2.0/${CHOST}" On the other hand, scim ebuild still uses has_multilib_profile && GTK2_CONFDIR="/etc/gtk-2.0/${CHOST}" GTK2_CONFDIR=${GTK2_CONFDIR:=/etc/gtk-2.0/} So if gtk+ is built before scim, /etc/gtk-2.0/${CHOST}/gtk.immodules (which doesn't contain a scim entry) takes precedence for GTK apps on non-multilib systems (can be verified with strace).
thank you for your report. x11-libs/gtk+ ebuilds uses CHOST-based directories since >=2.22.1-r1, bug #288549. 2.20.1-r1 is still in portage tree and uses old style. I'll fix all input methods soon.
> I'll fix all input methods soon. The bug can be closed now, correct?
Already fixed in CVS. Thanks.