[opensuse-factory] fcitx results with factory
Hi, I wanted to try fcitx. If INPUT_METHOD="fcitx" is set in my .profile after login there are outgoing connection attempts to 123.126.68.162 ... 123.126.68.171 in a round robin principle, to TCP port 80. If I try to input something chinese fcitx dies after the first pressed key (KDE). When I start it from the konsole it is terminated immediately with signal 6. Valgrind indicates invalid reads. Installed versions from factory: fcitx-4.2.4-1.1.x86_64 fcitx-cloudpinyin-0.2.2-1.1.x86_64 fcitx-googlepinyin-0.1.5-2.1.x86_64 fcitx-gtk2-4.2.4-1.1.x86_64 fcitx-gtk3-4.2.4-1.1.x86_64 fcitx-libpinyin-0.1.1-2.1.x86_64 fcitx-qt4-4.2.4-1.1.x86_64 fcitx-sunpinyin-0.3.7-1.1.x86_64 libfcitx-4_2_4-4.2.4-1.1.x86_64 Dieter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Jun 13, 2012 at 3:06 AM, dieter <d_werner@gmx.net> wrote:
Hi,
I wanted to try fcitx.
If INPUT_METHOD="fcitx" is set in my .profile after login there are outgoing connection attempts to 123.126.68.162 ... 123.126.68.171 in a round robin principle, to TCP port 80.
They're cloud pinyin query servers. Try disable cloud pinyin in System Settings - Locale - Input Method.
If I try to input something chinese fcitx dies after the first pressed key (KDE). When I start it from the konsole it is terminated immediately with signal 6. Valgrind indicates invalid reads.
Which input method engine do you use? if it is googlepinyin or sunpinyin, try to clean .fcitx/config/googlepinyin or .sunpinyin.
Installed versions from factory: fcitx-4.2.4-1.1.x86_64 fcitx-cloudpinyin-0.2.2-1.1.x86_64 fcitx-googlepinyin-0.1.5-2.1.x86_64 fcitx-gtk2-4.2.4-1.1.x86_64 fcitx-gtk3-4.2.4-1.1.x86_64 fcitx-libpinyin-0.1.1-2.1.x86_64 fcitx-qt4-4.2.4-1.1.x86_64 fcitx-sunpinyin-0.3.7-1.1.x86_64 libfcitx-4_2_4-4.2.4-1.1.x86_64
Dieter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 13 Jun 2012 13:16:25 +0800 Marguerite Su <i@marguerite.su> wrote:
On Wed, Jun 13, 2012 at 3:06 AM, dieter <d_werner@gmx.net> wrote:
123.126.68.162 ... 123.126.68.171 in a round robin principle, to TCP port 80.
They're cloud pinyin query servers. ok, that explains it.
Try disable cloud pinyin in System Settings - Locale - Input Method. I assume this is Systemeinstellungen - Regionales, but I have no option for Input Method there. I selected Pinyin (LibPinyin) in the tray icon instead.
If I try to input something chinese fcitx dies after the first pressed key (KDE). When I start it from the konsole it is terminated immediately with signal 6. Valgrind indicates invalid reads.
Which input method engine do you use? yes, it was googlepinyin CITX -- Get Signal No.: 6 Obtained 10 stack frames. /usr/bin/fcitx() [0x401359] /lib64/libc.so.6(+0x34da0) [0x7ffff7205da0] /lib64/libc.so.6(gsignal+0x35) [0x7ffff7205d25] /lib64/libc.so.6(abort+0x148) [0x7ffff72071a8] /lib64/libc.so.6(+0x72fbb) [0x7ffff7243fbb] /lib64/libc.so.6(+0x78b56) [0x7ffff7249b56] /usr/lib64/fcitx/fcitx-xkb.so(+0x42e0) [0x7fffef0bf2e0] /usr/lib64/libfcitx-core.so.0(FcitxModuleLoad+0x1cb) [0x7ffff7bd2076] /usr/lib64/libfcitx-core.so.0(FcitxInstanceCreate+0x3d3) [0x7ffff7bc0bb7] /usr/bin/fcitx() [0x4011aa]
seems not to be related to googlepinyin?
if it is googlepinyin or sunpinyin, try to clean .fcitx/config/googlepinyin or .sunpinyin.
after changing to libpinyin I get this crash.log, the crash happens again after switching to chinese input and pressing the first key: FCITX -- Get Signal No.: 11 Obtained 10 stack frames. fcitx() [0x401359] /lib64/libc.so.6(+0x34da0) [0x7f1036c65da0] /usr/lib64/libopencc.so.1(opencc_convert+0x16) [0x7f1029dc8e96] /usr/lib64/libopencc.so.1(opencc_convert_utf8+0xe6) [0x7f1029dc8fe6] /usr/lib64/fcitx/fcitx-chttrans.so(+0x2160) [0x7f1029fd0160] /usr/lib64/fcitx/fcitx-chttrans.so(+0x1ffc) [0x7f1029fcfffc] /usr/lib64/libfcitx-core.so.0(FcitxInstanceProcessOutputFilter+0x59) [0x7f1037627a3e] /usr/lib64/fcitx/fcitx-classic-ui.so(+0x134c5) [0x7f10214e44c5] /usr/lib64/fcitx/fcitx-classic-ui.so(+0x748d) [0x7f10214d848d] /usr/lib64/fcitx/fcitx-classic-ui.so(+0x7983) [0x7f10214d8983] Dieter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
在 2012年6月12日 星期二 21:06:05，dieter 写道：
Hi,
I wanted to try fcitx.
If INPUT_METHOD="fcitx" is set in my .profile after login there are outgoing connection attempts to 123.126.68.162 ... 123.126.68.171 in a round robin principle, to TCP port 80.
If I try to input something chinese fcitx dies after the first pressed key (KDE). When I start it from the konsole it is terminated immediately with signal 6. Valgrind indicates invalid reads.
Installed versions from factory: fcitx-4.2.4-1.1.x86_64 fcitx-cloudpinyin-0.2.2-1.1.x86_64 fcitx-googlepinyin-0.1.5-2.1.x86_64 fcitx-gtk2-4.2.4-1.1.x86_64 fcitx-gtk3-4.2.4-1.1.x86_64 fcitx-libpinyin-0.1.1-2.1.x86_64 fcitx-qt4-4.2.4-1.1.x86_64 fcitx-sunpinyin-0.3.7-1.1.x86_64 libfcitx-4_2_4-4.2.4-1.1.x86_64
Dieter
Hi, could you paste your ~/.config/fcitx/log/crash.log some where? If it contains fcitx-googlepinyin.so, then you might want to uninstall it. Actually googlepinyin is quite buggy, as maintainer I don't recommend to use it. If so you can send your ~/.config/fcitx/googlepinyin to me.
participants (3)
-
dieter -
Marguerite Su -
Weng Xuetian