Description of problem: Hello I am facing problem in using scim in Fedora -9. I have installed the required packages but when I start scim, it crashes. The crash report is posted here http://salilgk.googlepages.com/im-chooser-bugreport.txt Any pointers on how to fix this Thanks Salil Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I can not access http://salilgk.googlepages.com/im-chooser-bugreport.txt. Could you attach this file on this bug?
How you updated to the latest im-chooser and imsettings packages from F9 Updates?
Created attachment 311240 [details] output scim start This is what I got output when I tried to start scim component
Created attachment 311263 [details] scim malalayam is installed like this
Where do you see that output and how are you starting scim?
(In reply to comment #3) > Created an attachment (id=311240) [edit] > output scim start > > This is what I got output when I tried to start scim component I only saw error output from im-chooser. Which version of im-chooser do you use? Did you update im-chooser?
I used gui for starting im-chooser. Then it dumped so I tried to execute /usr/bin/im-chooser there also it dumped. The following is the output. >>>>> [root@Studio ~]# /usr/bin/im-chooser (im-chooser:2993): IMSettings-WARNING **: Failed to invoke a method `WhatInputMethodIsRunning': Failed to open file '/tmp/scim_conf:xim::0.0-root': No such file or directory Segmentation fault <<<<< [root@Studio ~]# /usr/bin/im-chooser --version GNOME im-chooser 0.99.6 Thanks
Please use `rpm -q im-chooser` to check im-chooser's rpm version. If it is early than 0.99.6-5, please use `yum update im-chooser` to update it.
I thinks it is im-chooser's problem.
Thanks for the advice. I have updated im-chooser and it works. Now could you please let me know how to learn the keyboard map for Malayalayam itran input method. Any pointers would be really appreciated. thanks Salil
better ask on fedora-i18n-list. *** This bug has been marked as a duplicate of 445129 ***