Description of problem: Initially, ibus daemon was not running when I first visited Fedora>Preferences>Input Method Selector. After being prompted when selectin the iBus method, the iBus daemon was started through the choice. However, it fell over eventually. Version-Release number of selected component: ibus-1.5.3-1.fc19 Additional info: reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/libexec/ibus-ui-gtk3 crash_function: panel_switch_engine executable: /usr/libexec/ibus-ui-gtk3 kernel: 3.10.10-200.fc19.x86_64 runlevel: N 5 uid: 1000 var_log_messages: Sep 3 17:47:57 stelline abrt[9023]: Saved core dump of pid 9010 (/usr/libexec/ibus-ui-gtk3) to /var/tmp/abrt/ccpp-2013-09-03-17:47:57-9010 (14462976 bytes) Truncated backtrace: Thread no. 1 (9 frames) #4 panel_switch_engine at panel.c:3481 #5 panel_update_engines at panel.c:4122 #6 panel_set_config at panel.c:1574 #7 application_config_name_owner_changed_cb at application.c:308 #8 _application_config_name_owner_changed_cb_gd_bus_signal_callback at application.c:180 #9 emit_signal_instance_in_idle_cb at gdbusconnection.c:3715 #14 gtk_main at gtkmain.c:1156 #15 application_run at application.c:217 #16 application_main at application.c:340 Potential duplicate: bug 862031
Created attachment 793283 [details] File: backtrace
Created attachment 793284 [details] File: cgroup
Created attachment 793285 [details] File: core_backtrace
Created attachment 793286 [details] File: dso_list
Created attachment 793287 [details] File: environ
Created attachment 793288 [details] File: limits
Created attachment 793289 [details] File: maps
Created attachment 793290 [details] File: open_fds
Created attachment 793291 [details] File: proc_pid_status
(In reply to tom.suzuki from comment #1) > Created attachment 793283 [details] > File: backtrace > #0 0x000000372dc35a19 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 > #1 0x000000372dc37128 in __GI_abort () at abort.c:90 > #2 0x000000373006bbc6 in g_assertion_message (domain=domain@entry=0x41947d "IBUS", file=file@entry=0x41aac1 "panel.c", line=line@entry=3481, func=func@entry=0x41b640 <__PRETTY_FUNCTION__.53329> "panel_switch_engine", message=<optimized out>) at gtestutils.c:1912 > #3 0x000000373006bc24 in g_assertion_message_expr (domain=domain@entry=0x41947d "IBUS", file=file@entry=0x41aac1 "panel.c", line=line@entry=3481, func=func@entry=0x41b640 <__PRETTY_FUNCTION__.53329> "panel_switch_engine", expr=expr@entry=0x41b010 "i >= 0 && i < m_engines.length") at gtestutils.c:1923 > #4 0x00000000004117f7 in panel_switch_engine (self=0x244c390, i=<optimized out>, force=<optimized out>) at panel.c:3481 > #5 0x000000000041227e in panel_update_engines (self=self@entry=0x244c390, var_engines=var_engines@entry=0x7fcec40d7e30, var_order=var_order@entry=0x7fcec400a4d0) at panel.c:4122 > #6 0x0000000000412a96 in panel_set_config (self=0x244c390, config=<optimized out>) at panel.c:1574 > #7 0x000000000040842d in application_config_name_owner_changed_cb (parameters=<optimized out>, signal_name=<optimized out>, interface_name=<optimized out>, object_path=<optimized out>, sender_name=<optimized out>, connection=<optimized out>, self=0x2407400) at application.c:308 I cannot reproduce your backtrace. Are you still able to reproduce your backtrace? Which keymap do you use? % setxkbmap -query
*** This bug has been marked as a duplicate of bug 1037999 ***