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(pinyin_context_t*) executable: /usr/libexec/ibus-engine-libpinyin journald_cursor: s=f9047c3871b9426fb1457b843e4962ba;i=2be43;b=a2c85faaa45f4919a598643806057a19;m=10704f78ad;t=58937579e8528;x=34c91ce58520a188 kernel: 5.0.16-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 pinyin_save(pinyin_context_t*) at pinyin.cpp:736 #1 PY::LibPinyinBackEnd::clearPinyinUserData(char const*) at PYLibPinyin.cc:307 #2 PY::PinyinConfig::valueChanged(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, _GVariant*) at /usr/include/c++/9/bits/basic_string.h:2297 #3 PY::LibPinyinConfig::valueChangedCallback(_GSettings*, char const*, PY::LibPinyinConfig*) at /usr/include/c++/9/bits/char_traits.h:300 Potential duplicate: bug 1579078
Created attachment 1570766 [details] File: backtrace
Created attachment 1570767 [details] File: cgroup
Created attachment 1570768 [details] File: core_backtrace
Created attachment 1570769 [details] File: cpuinfo
Created attachment 1570770 [details] File: dso_list
Created attachment 1570771 [details] File: environ
Created attachment 1570772 [details] File: exploitable
Created attachment 1570773 [details] File: limits
Created attachment 1570774 [details] File: maps
Created attachment 1570775 [details] File: mountinfo
Created attachment 1570776 [details] File: open_fds
Created attachment 1570777 [details] File: proc_pid_status
Could you explain the detailed steps to reproduce this issue?
I don't have any reproduction steps for this issue. I was not doing anything related to ibus at the time the issue occurred; it must have been part of a background process.
I think this bug only happens when dnf upgrade, and write one patch to mitigate this issue.