Bug 903270

Summary: [abrt] ibus-mozc-1.6.1187.102-1.fc18: ibus_config_get_value: Process /usr/libexec/ibus-engine-mozc was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: denkyoku plus <omoikanearma>
Component: mozcAssignee: Akira TAGOH <tagoh>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: i18n-bugs, tagoh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b7c3676bfbc429987eb2c877d84ef2c1f433b8e6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-22 04:35:51 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: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: smolt_data none

Description denkyoku plus 2013-01-23 15:47:56 UTC 
Version-Release number of selected component:
ibus-mozc-1.6.1187.102-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/ibus-engine-mozc --ibus
crash_function: ibus_config_get_value
executable:     /usr/libexec/ibus-engine-mozc
kernel:         3.7.2-204.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (2 frames)
 #4 ibus_config_get_value at ibusconfig.c:394
 #5 mozc::ibus::MozcEngine::InitRendererConfig at unix/ibus/mozc_engine.cc:477
Comment 1 denkyoku plus 2013-01-23 15:48:03 UTC 
Created attachment 686048 [details]
File: backtrace
Comment 2 denkyoku plus 2013-01-23 15:48:08 UTC 
Created attachment 686049 [details]
File: cgroup
Comment 3 denkyoku plus 2013-01-23 15:48:11 UTC 
Created attachment 686050 [details]
File: core_backtrace
Comment 4 denkyoku plus 2013-01-23 15:48:16 UTC 
Created attachment 686051 [details]
File: dso_list
Comment 5 denkyoku plus 2013-01-23 15:48:19 UTC 
Created attachment 686052 [details]
File: environ
Comment 6 denkyoku plus 2013-01-23 15:48:23 UTC 
Created attachment 686053 [details]
File: limits
Comment 7 denkyoku plus 2013-01-23 15:48:29 UTC 
Created attachment 686054 [details]
File: maps
Comment 8 denkyoku plus 2013-01-23 15:48:33 UTC 
Created attachment 686055 [details]
File: open_fds
Comment 9 denkyoku plus 2013-01-23 15:48:37 UTC 
Created attachment 686056 [details]
File: proc_pid_status
Comment 10 denkyoku plus 2013-01-23 15:48:42 UTC 
Created attachment 686057 [details]
File: var_log_messages
Comment 11 denkyoku plus 2013-01-23 15:48:47 UTC 
Created attachment 686058 [details]
File: smolt_data
Comment 12 Fedora End Of Life 2013-12-21 10:45:15 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 13 Akira TAGOH 2014-01-22 04:35:51 UTC 
That looks like fixed in the latest version. if you still see this issue, please reopen or file another bug. thanks.