Bug 958112

Summary: [abrt] ibus-1.5.1-2.fc18: panel_switch_engine: Process /usr/libexec/ibus-ui-gtk3 was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: wainy.163
Component: ibusAssignee: fujiwara <tfujiwar>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: i18n-bugs, john.haxby, samtygier, shawn.p.huang, tfujiwar
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:6d8a757ef0c4bf260d6e39481e89158a5a1503f7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-28 04:26:26 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: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description wainy.163 2013-04-30 12:25:57 UTC 
Description of problem:
I don't know.

Version-Release number of selected component:
ibus-1.5.1-2.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/ibus-ui-gtk3
core_backtrace: 
crash_function: panel_switch_engine
executable:     /usr/libexec/ibus-ui-gtk3
kernel:         3.8.9-200.fc18.i686
uid:            1000
ureports_counter: 1
var_log_messages: May  1 04:20:12 local0019d22cb4b2 abrt[1753]: Saved core dump of pid 1739 (/usr/libexec/ibus-ui-gtk3) to /var/tmp/abrt/ccpp-2013-05-01-04:20:12-1739 (11407360 bytes)
xsession_errors: 

Truncated backtrace:
Thread no. 1 (9 frames)
 #5 panel_switch_engine at panel.c:3048
 #6 panel_update_engines at panel.c:3589
 #7 panel_set_config at panel.c:1143
 #8 application_config_name_owner_changed_cb at application.c:308
 #9 _application_config_name_owner_changed_cb_gd_bus_signal_callback at application.c:180
 #10 emit_signal_instance_in_idle_cb at gdbusconnection.c:3715
 #16 gtk_main at gtkmain.c:1160
 #17 application_run at application.c:217
 #18 application_main at application.c:340

Potential duplicate: bug 862031
Comment 1 wainy.163 2013-04-30 12:26:00 UTC 
Created attachment 741863 [details]
File: backtrace
Comment 2 wainy.163 2013-04-30 12:26:03 UTC 
Created attachment 741864 [details]
File: cgroup
Comment 3 wainy.163 2013-04-30 12:26:10 UTC 
Created attachment 741865 [details]
File: dso_list
Comment 4 wainy.163 2013-04-30 12:26:13 UTC 
Created attachment 741866 [details]
File: environ
Comment 5 wainy.163 2013-04-30 12:26:16 UTC 
Created attachment 741867 [details]
File: limits
Comment 6 wainy.163 2013-04-30 12:26:18 UTC 
Created attachment 741868 [details]
File: maps
Comment 7 wainy.163 2013-04-30 12:26:21 UTC 
Created attachment 741869 [details]
File: open_fds
Comment 8 wainy.163 2013-04-30 12:26:23 UTC 
Created attachment 741870 [details]
File: proc_pid_status
Comment 9 fujiwara 2013-05-07 03:26:00 UTC 
(In reply to comment #0)
>  #5 panel_switch_engine at panel.c:3048
>  #6 panel_update_engines at panel.c:3589
>  #7 panel_set_config at panel.c:1143
>  #8 application_config_name_owner_changed_cb at application.c:308
>  #9 _application_config_name_owner_changed_cb_gd_bus_signal_callback at

I cannot reproduce your problem.
I think you don't reproduce your problem with a new user account instead of the current user account.
Comment 10 john.haxby@oracle.com 2013-06-04 09:15:10 UTC 
I think this happens when I log out or reboot: when I next log in I see the crash report.  It happens every time; I'm using KDE.

reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/libexec/ibus-ui-gtk3
crash_function: panel_switch_engine
executable:     /usr/libexec/ibus-ui-gtk3
kernel:         3.9.4-200.fc18.x86_64
package:        ibus-1.5.1-2.fc18
reason:         Process /usr/libexec/ibus-ui-gtk3 was killed by signal 6 (SIGABRT)
runlevel:       N 5
uid:            1000
xsession_errors:
Comment 11 john.haxby@oracle.com 2013-06-04 09:43:02 UTC 
Does the backtrace help?   Would the core dump be more useful?  (I can put it somewhere you can get to it.)

I used KDE on a couple of machines and it only happens on this one so there's something interesting about my environment on this machine.  It has obviously happened to at least one other person in the past (see possible duplicate).
Comment 12 fujiwara 2013-06-05 02:32:50 UTC 
(In reply to John Haxby from comment #11)
> Does the backtrace help?   Would the core dump be more useful?  (I can put
> it somewhere you can get to it.)

No, it does not.
I already asked a question in Comment #9.

> 
> I used KDE on a couple of machines and it only happens on this one so
> there's something interesting about my environment on this machine.  It has
> obviously happened to at least one other person in the past (see possible
> duplicate).

I cannot reproduce your problem.
Are you able to reproduce your problem with a new user account instead of the current user account?
Comment 13 john.haxby@oracle.com 2013-08-30 08:37:23 UTC 
My apologies.   I found out what the problem was and fixed it a while ago and completely forgot to update the bug.

I think this stems from the fact that my various profile entries are quite old: my home directory dates back some years (F12?  possibly even earlier) and the ibus settings would have been created then.

When I ran ibus-setup I noticed that there were no defined input methods.  Adding at least one allowed ibus-ui-gtk3 to start normally.  Deleting the input method(s)  in ibus-setup simply reverts the list to the default single entry so I don't really know how I got myself into this mess.

I can't re-open this bug, but even if I could I suspect that it should just be closed again.   If someone else comes across this then the fix is to simply define at least one input method in ibus-setup.