[Fedora-i18n-bugs] [Bug 1586296] New: [abrt] ibus-libpinyin: pinyin_save(): ibus-engine-libpinyin killed by SIGSEGV

https://bugzilla.redhat.com/show_bug.cgi?id=1586296

Bug ID: 1586296
           Summary: [abrt] ibus-libpinyin: pinyin_save():
                    ibus-engine-libpinyin killed by SIGSEGV
           Product: Fedora
           Version: 28
         Component: ibus-libpinyin
          Assignee: [e-mail]
          Reporter: [e-mail]
        QA Contact: [e-mail]
                CC: [e-mail],
                    [e-mail], [e-mail]

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
executable:     /usr/libexec/ibus-engine-libpinyin
journald_cursor:
s=52e1c1c145d84b2cb155ffe9c107ba83;i=3b1b73;b=dae3461a0e2945be9e92f08f92ce0837;m=321644364f;t=56ded81d26ea8;x=106dd56aa4eeefd0
kernel:         4.16.13-300.fc28.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(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
 #8 g_settings_real_change_event at gsettings.c:386
 #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 gclosure.c:1604
 #12 _g_closure_invoke_va at gclosure.c:867
 #15 settings_backend_path_changed at gsettings.c:461

Potential duplicate: bug 1568208

[Fedora-i18n-bugs] [Bug 1586296] [abrt] ibus-libpinyin: pinyin_save(): ibus-engine-libpinyin killed by SIGSEGV

https://bugzilla.redhat.com/show_bug.cgi?id=1586296

--- Comment #13 from Peng Wu  ---
Could you provide the steps to reproduce this bug?