Description of problem: ibus-libpinyin crashed on startup after I updated the system with "yum update." Version-Release number of selected component: ibus-libpinyin-1.4.93-4.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-libpinyin --ibus crash_function: PY::PunctEditor::moveCursorRight executable: /usr/libexec/ibus-engine-libpinyin kernel: 3.6.7-5.fc18.x86_64 uid: 1000 var_log_messages: Dec 14 09:28:25 localhost abrt[25028]: Saved core dump of pid 30342 (/usr/libexec/ibus-engine-libpinyin) to /var/spool/abrt/ccpp-2012-12-14-09:28:24-30342 (24297472 bytes) Truncated backtrace: Thread no. 1 (8 frames) #4 PY::PunctEditor::moveCursorRight at PYPunctEditor.cc:305 #5 PY::PunctEditor::processKeyEvent at PYPunctEditor.cc:186 #6 PY::LibPinyinPinyinEngine::processKeyEvent at PYPPinyinEngine.cc:173 #7 _ibus_marshal_BOOLEAN__UINT_UINT_UINT at ibusmarshalers.c:290 #12 ibus_engine_service_method_call at ibusengine.c:816 #13 call_in_idle_cb at gdbusconnection.c:4737 #18 ibus_main at ibusshare.c:295 #19 start_component at PYMain.cc:152
Created attachment 665007 [details] File: backtrace
Created attachment 665008 [details] File: cgroup
Created attachment 665009 [details] File: core_backtrace
Created attachment 665010 [details] File: dso_list
Created attachment 665011 [details] File: environ
Created attachment 665012 [details] File: limits
Created attachment 665013 [details] File: maps
Created attachment 665014 [details] File: open_fds
Created attachment 665015 [details] File: proc_pid_status
Could you provide what punctuation are you inputting?
It crashed during log-in process, so I was not actually inputting anything at the time. But the settings are set for Full width, Full punctuations, and Traditional Chinese. Please let me know if that's not what you meant. P.S. libpinyin works really well. Thank you very much!
Welcome. Does it occur frequently or sometimes? Does it occur with a new user account? I need to re-produce this bug first. Either the steps to re-produce it, or the user data to re-produce it.
It only occured that one time, and I have not been able to reproduce it since.
As it only occurs once, close bug now. If new crash exists, feel free to report it again.