Red Hat Bugzilla – Bug 195441
[FC5] cannot activate scim setup on Western desktop
Last modified: 2007-11-30 17:11:35 EST
Description of problem: It seems that the version currently in updates-testing (scim-1.4.4-9.3.fc5) does not allow activating scim inputs on anything other than pre-defined CJK locales (e.g. zh_CN.UTF-8). I have not been successful in triggering the layout under en_CA.UTF-8, even though it worked before the update, and I have the necessary symlink in ~/.xinput.d/default->/etc/X11/xinit/xinput.d/scim (also tried creating ~/.xinput.d/en_CA with no results). Version-Release number of selected component (if applicable): scim-1.4.4-9.3.fc5 How reproducible: always Steps to Reproduce: 1. Configure scim under en_US or en_CA locales (e.g. by running im-switch -s scim). 2. Try to switch to any SCIM locale by either key combos, or by left-clicking on the notification area applet. SCIM shows no signs of life. 3. This only works if an application is started in, say, zh_CN.UTF-8 locale -- then SCIM works as expected. Additional info: I have reproduced this problem on 2 different machines, plus at least one other person is seeing the same behaviour (http://mricon.livejournal.com/329742.html?thread=544270#t544270).
*** Bug 195442 has been marked as a duplicate of this bug. ***
------- Additional Comments From petersen@redhat.com 2006-06-13 04:13 EST ------- Hmm strange, works ok for me. And you have xorg-x11-xinit-1.0.1-2, right?
------- Additional Comments From petersen@redhat.com 2006-06-13 07:48 EST ------- Do you see any yum upgrade log errors. I found a %post error: it seems the scim libraries and gtimm module were not linked against libstdc++so7 even though they were compiled with it. Unfortunately this time I mainly just tested upgrading the main package not scim-libs since the only change packaging change was scim obsoleting scim-qtimm, and worse the package was just pushed to final. :-(
------- Additional Comments From petersen@redhat.com 2006-06-13 07:52 EST ------- Ok, thanks for the report: I think this is because I forgot to update the libtool tweaking for libstdc++so7 for gcc-4.1.1, which broken libtool linking of the .so files unfortunately.