Bug 1711631

Summary: [abrt] ibus-libpinyin: pinyin_save(pinyin_context_t*)(): ibus-engine-libpinyin killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Sean Burke <leftmostcat>
Component: ibus-libpinyinAssignee: Peng Wu <pwu>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: i18n-bugs, petersen, pwu
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ba4308b55bb755f839610f13039704f5a48fbbdd
Whiteboard: abrt_hash:2907b6d4b730ec4a10a6bea50fea98c87d3a4241;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-10 06:12:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Sean Burke 2019-05-19 06:08:41 UTC 
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
Comment 1 Sean Burke 2019-05-19 06:08:43 UTC 
Created attachment 1570766 [details]
File: backtrace
Comment 2 Sean Burke 2019-05-19 06:08:44 UTC 
Created attachment 1570767 [details]
File: cgroup
Comment 3 Sean Burke 2019-05-19 06:08:45 UTC 
Created attachment 1570768 [details]
File: core_backtrace
Comment 4 Sean Burke 2019-05-19 06:08:46 UTC 
Created attachment 1570769 [details]
File: cpuinfo
Comment 5 Sean Burke 2019-05-19 06:08:47 UTC 
Created attachment 1570770 [details]
File: dso_list
Comment 6 Sean Burke 2019-05-19 06:08:48 UTC 
Created attachment 1570771 [details]
File: environ
Comment 7 Sean Burke 2019-05-19 06:08:49 UTC 
Created attachment 1570772 [details]
File: exploitable
Comment 8 Sean Burke 2019-05-19 06:08:50 UTC 
Created attachment 1570773 [details]
File: limits
Comment 9 Sean Burke 2019-05-19 06:08:51 UTC 
Created attachment 1570774 [details]
File: maps
Comment 10 Sean Burke 2019-05-19 06:08:52 UTC 
Created attachment 1570775 [details]
File: mountinfo
Comment 11 Sean Burke 2019-05-19 06:08:52 UTC 
Created attachment 1570776 [details]
File: open_fds
Comment 12 Sean Burke 2019-05-19 06:08:53 UTC 
Created attachment 1570777 [details]
File: proc_pid_status
Comment 13 Peng Wu 2019-05-20 07:09:34 UTC 
Could you explain the detailed steps to reproduce this issue?
Comment 14 Sean Burke 2019-05-21 05:51:20 UTC 
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.
Comment 15 Peng Wu 2020-04-10 06:12:12 UTC 
I think this bug only happens when dnf upgrade, and write one patch to mitigate this issue.