Description of problem: Crash when updating system Version-Release number of selected component: ibus-libpinyin-1.11.0-2.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-libpinyin --ibus crash_function: pinyin_save executable: /usr/libexec/ibus-engine-libpinyin journald_cursor: s=cc3b4d7aa103497a99d675649b9ae013;i=94c7;b=13573ad620e541ff8cacc1ad1ceca0c3;m=eea6a32;t=584549ca4b236;x=245f7212fc098115 kernel: 5.0.0-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 pinyin_save at pinyin.cpp:736 #1 PY::LibPinyinBackEnd::clearPinyinUserData at PYLibPinyin.cc:307 #2 PY::PinyinConfig::valueChanged at /usr/include/c++/9/bits/basic_string.h:2297 #3 PY::LibPinyinConfig::valueChangedCallback at /usr/include/c++/9/bits/char_traits.h:300 #8 g_settings_real_change_event at ../gio/gsettings.c:391 #9 ffi_call_unix64 at ../src/x86/unix64.S:76 #10 ffi_call at ../src/x86/ffi64.c:525 #11 g_cclosure_marshal_generic_va at ../gobject/gclosure.c:1614 #12 _g_closure_invoke_va at ../gobject/gclosure.c:873 #15 settings_backend_path_changed at ../gio/gsettings.c:466 Potential duplicate: bug 1649100
Created attachment 1545042 [details] File: backtrace
Created attachment 1545043 [details] File: cgroup
Created attachment 1545044 [details] File: core_backtrace
Created attachment 1545045 [details] File: cpuinfo
Created attachment 1545046 [details] File: dso_list
Created attachment 1545047 [details] File: environ
Created attachment 1545048 [details] File: limits
Created attachment 1545049 [details] File: maps
Created attachment 1545050 [details] File: mountinfo
Created attachment 1545051 [details] File: open_fds
Created attachment 1545052 [details] File: proc_pid_status
Created attachment 1545053 [details] File: exploitable
Similar problem has been detected: runing update: dnf upgrade reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-libpinyin --ibus crash_function: pinyin_save executable: /usr/libexec/ibus-engine-libpinyin journald_cursor: s=da5ad80e525e4ff08bf4c205723ad523;i=331f;b=d7695066fe5a459984362bd576f64b63;m=41f02be5;t=5892670578326;x=59eae0bc76de8f97 kernel: 5.0.9-301.fc30.x86_64 package: ibus-libpinyin-1.11.0-2.fc30 reason: ibus-engine-libpinyin killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: 1. dnnf -y update 2. occur reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-libpinyin --ibus crash_function: pinyin_save executable: /usr/libexec/ibus-engine-libpinyin journald_cursor: s=7b59baba04774aa28e83586a2efedf44;i=2550d;b=b90cf6cab9784b048ceac771ff128665;m=25bf547c;t=5892b1193ac16;x=554eaec1dd14426c kernel: 5.0.16-300.fc30.x86_64 package: ibus-libpinyin-1.11.0-2.fc30 reason: ibus-engine-libpinyin killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1711620 has been marked as a duplicate of this bug. ***
Could you explain the detailed steps to reproduce this issue?
(In reply to Peng Wu from comment #16) > Could you explain the detailed steps to reproduce this issue? It is reproducible if one updates ibus in a logged-in session with ibus running.
*** Bug 1733428 has been marked as a duplicate of this bug. ***
Fixed in https://github.com/epico/ibus-libpinyin/commit/197e1b6c16608956141cd3668d35e4c22d18027e .
*** Bug 1739896 has been marked as a duplicate of this bug. ***
*** Bug 1743022 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I don't recall what I was doing. I only saw the notification of a crash in libpinyin much later. reporter: libreport-2.10.1 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-libpinyin --ibus crash_function: pinyin_save executable: /usr/libexec/ibus-engine-libpinyin journald_cursor: s=d28006acb2b843d780327c79166993ce;i=e9c8;b=cba4de02359644e98f4656153a2944c2;m=368a761bc;t=5907b92c0f128;x=af383aba895e5268 kernel: 5.1.20-300.fc30.x86_64 package: ibus-libpinyin-1.11.1-1.fc30 reason: ibus-engine-libpinyin killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Hi Corey Ashford, Are you upgrading the rpm packages? Regards, Peng
(In reply to Peng Wu from comment #23) > Hi Corey Ashford, > > Are you upgrading the rpm packages? > I'm not sure how old the notification is, so it might have happened during a previous upgrade. I'll file again if it happens while not upgrading.
Okay, thanks for comments.
*** Bug 1756241 has been marked as a duplicate of this bug. ***
I think this bug only happens when dnf upgrade, and write one patch to mitigate this issue.
*** Bug 1758852 has been marked as a duplicate of this bug. ***