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
Created attachment 741863 [details] File: backtrace
Created attachment 741864 [details] File: cgroup
Created attachment 741865 [details] File: dso_list
Created attachment 741866 [details] File: environ
Created attachment 741867 [details] File: limits
Created attachment 741868 [details] File: maps
Created attachment 741869 [details] File: open_fds
Created attachment 741870 [details] File: proc_pid_status
(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.
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:
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).
(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?
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.