Version-Release number of selected component: ibus-libpinyin-1.10.0-1.fc28 Additional info: reporter: libreport-2.9.5 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=52e1c1c145d84b2cb155ffe9c107ba83;i=38605b;b=fd25554919fb41e0be205b3fff0dd9a5;m=4ab68a27;t=56c5aa1cab265;x=e77d720726849826 kernel: 4.16.8-300.fc28.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 PYLibPinyin.h:60 #3 PY::LibPinyinConfig::valueChangedCallback(_GSettings*, char const*, PY::LibPinyinConfig*) at /usr/include/c++/8/bits/char_traits.h:320
Created attachment 1437677 [details] File: backtrace
Created attachment 1437678 [details] File: cgroup
Created attachment 1437679 [details] File: core_backtrace
Created attachment 1437680 [details] File: cpuinfo
Created attachment 1437681 [details] File: dso_list
Created attachment 1437682 [details] File: environ
Created attachment 1437683 [details] File: exploitable
Created attachment 1437684 [details] File: limits
Created attachment 1437685 [details] File: maps
Created attachment 1437686 [details] File: mountinfo
Created attachment 1437687 [details] File: open_fds
Created attachment 1437688 [details] File: proc_pid_status
Could you describe how to reproduce this issue? It seems pinyin_save got null pointer. After switch to ibus-libpinyin, the pointer is not null I think.
As ibus-libpinyin 1.11.0 and libpinyin 2.3.0 are released, close bug.