Red Hat Bugzilla – Bug 1003133
[abrt] ibus-libpinyin-1.6.91-2.fc19: g_assertion_message: Process /usr/libexec/ibus-engine-libpinyin was killed by signal 6 (SIGABRT)
Last modified: 2013-09-16 23:16:50 EDT
Version-Release number of selected component:
cmdline: /usr/libexec/ibus-engine-libpinyin --ibus
runlevel: N 5
var_log_messages: Aug 31 08:05:03 localhost abrt: Saved core dump of pid 1480 (/usr/libexec/ibus-engine-libpinyin) to /var/tmp/abrt/ccpp-2013-08-31-08:05:02-1480 (18501632 bytes)
Thread no. 1 (10 frames)
#2 g_assertion_message at /lib64/libglib-2.0.so.0
#3 g_assertion_message_expr at /lib64/libglib-2.0.so.0
#4 PY::PunctEditor::moveCursorToBegin at PYPunctEditor.cc:318
#5 PY::PunctEditor::processKeyEvent at PYPunctEditor.cc:191
#6 PY::LibPinyinPinyinEngine::processKeyEvent at PYPPinyinEngine.cc:183
#7 _ibus_marshal_BOOLEAN__UINT_UINT_UINT at ibusmarshalers.c:290
#8 g_closure_invoke at /lib64/libgobject-2.0.so.0
#9 signal_emit_unlocked_R at /lib64/libgobject-2.0.so.0
#10 g_signal_emit_valist at /lib64/libgobject-2.0.so.0
#11 g_signal_emit at /lib64/libgobject-2.0.so.0
Created attachment 792330 [details]
Created attachment 792331 [details]
Created attachment 792332 [details]
Created attachment 792333 [details]
Created attachment 792334 [details]
Created attachment 792335 [details]
Created attachment 792336 [details]
Created attachment 792337 [details]
Created attachment 792338 [details]
Could you provide what are you inputting?
I need to re-produce this bug first.
Well, I was cleaning the keyboard with a cloth when ibus-libpinyin crashed.
Guess okay to close this bug, if it occurs rarely?
I suppose so.
Close bug, if this bug occurs again, feel free to report it, thanks.