I don’t know how to solve it ?
Loading socket Config module …
I have the same problem for almost any Yast related application.
again again again ???>:(
===================================================================
Loading socket Config module …
Creating backend …
Loading x11 FrontEnd module …
Failed to load x11 FrontEnd module.
Loading simple Config module …
Creating backend …
Reading pinyin phrase lib failed
<00001133>:scim_skk_imengine.cpp:122 > Create SKK Factory :
<00001134>:scim_skk_imengine.cpp:123 > Lang : ja_JP
<00001135>:scim_skk_imengine.cpp:124 > UUID : ec43125f-f9d3-4a77-8096-de3a35290ba9
Loading socket FrontEnd module …
Starting SCIM as daemon …
Loading socket Config module …
Creating backend …
Loading x11 FrontEnd module …
Failed to load x11 FrontEnd module.
Loading simple Config module …
Creating backend …
Reading pinyin phrase lib failed
<00001133>:scim_skk_imengine.cpp:122 > Create SKK Factory :
<00001134>:scim_skk_imengine.cpp:123 > Lang : ja_JP
<00001135>:scim_skk_imengine.cpp:124 > UUID : ec43125f-f9d3-4a77-8096-de3a35290ba9
Loading socket FrontEnd module …
Starting SCIM as daemon …
Loading socket Config module …
Creating backend …
Loading x11 FrontEnd module …
Failed to load x11 FrontEnd module.
Loading simple Config module …
Creating backend …
Reading pinyin phrase lib failed
<00001133>:scim_skk_imengine.cpp:122 > Create SKK Factory :
<00001134>:scim_skk_imengine.cpp:123 > Lang : ja_JP
<00001135>:scim_skk_imengine.cpp:124 > UUID : ec43125f-f9d3-4a77-8096-de3a35290ba9
Loading socket FrontEnd module …
Starting SCIM as daemon …
Anyone has found the fix? I have the same problem.
RickyWong wrote:
> Anyone has found the fix? I have the same problem.
found a fix?? i don’t even come close to understanding the problem!!
(but, i freely admit i’m pretty dense!)
i’d suggest someone with the problem read this
<http://tinyurl.com/anel> and then post again by using actual
language to describe (for example):
-what is done (clicked, typed, etc) to cause the output in yawnp0426’s
first and second posting?
-where is the output seen? a log file perhaps? which? or what?
-what version of openSUSE is in use?
-what display environment?
-when did this begin? (immediately after install or suddenly right
after you did what?)
-did it begin after an update? WHICH update?
-have you already tried backing out the suspect update?
-have you tried restoring the system from your current backup?
-etc etc etc etc etc
–
natural_pilot
I used Software.openSUSE.org to upgrade Pidgin. I knew I needed 2.5.7 to get Yahoo working again, but chose 2.5.8 . This required a libpurple upgrade, but broke Pidgin as described in this bug.
I then downgraded Pidgin to 2.5.7, plus dependencies, and the problem went away.
Never mind. I guess this must have been a coincidence. The error is no longer in my face, but it is still there.