Version-Release number of selected component: ibus-1.5.16-4.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: ibus-daemon --xim --panel disable crash_function: bus_dbus_impl_connection_filter_cb executable: /usr/bin/ibus-daemon journald_cursor: s=976ceac0a19546fe967615f8e533c44a;i=4f2cf;b=73b5f0ebb3b44587aea0f5d446501fe5;m=179fd775e;t=5554809ef57f5;x=12a23f6072d45643 kernel: 4.11.11-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 982836
Created attachment 1305246 [details] File: backtrace
Created attachment 1305247 [details] File: cgroup
Created attachment 1305248 [details] File: core_backtrace
Created attachment 1305249 [details] File: cpuinfo
Created attachment 1305250 [details] File: dso_list
Created attachment 1305251 [details] File: environ
Created attachment 1305252 [details] File: limits
Created attachment 1305253 [details] File: maps
Created attachment 1305254 [details] File: open_fds
Created attachment 1305255 [details] File: proc_pid_status
Created attachment 1305256 [details] File: var_log_messages
I cannot reproduce your backtrace. (In reply to Gwendal from comment #1) > Created attachment 1305246 [details] > File: backtrace #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00007fa9cb83a470 in __GI_abort () at abort.c:89 #2 0x00007fa9cbe6270d in g_assertion_message (domain=domain@entry=0x55850b2f2dda "IBUS", file=file@entry=0x55850b2f3244 "dbusimpl.c", line=line@entry=1473, func=func@entry=0x55850b2f38c0 <__func__.26452> "bus_dbus_impl_connection_filter_cb", message=message@entry=0x7fa9b400e0f0 "assertion failed: (connection != NULL)") at gtestutils.c:2433 #3 0x00007fa9cbe6279a in g_assertion_message_expr (domain=domain@entry=0x55850b2f2dda "IBUS", file=file@entry=0x55850b2f3244 "dbusimpl.c", line=line@entry=1473, func=func@entry=0x55850b2f38c0 <__func__.26452> "bus_dbus_impl_connection_filter_cb", expr=expr@entry=0x55850b2f3291 "connection != NULL") at gtestutils.c:2456 #4 0x000055850b2e23b6 in bus_dbus_impl_connection_filter_cb (dbus_connection=<optimized out>, message=0x55850cd44d40, incoming=0, user_data=0x55850ca72830) at dbusimpl.c:1473 #5 0x00007fa9cc40e59e in on_worker_message_about_to_be_sent (worker=<optimized out>, message=0x55850cd44d40, user_data=0x7fa9b8005c90) at gdbusconnection.c:2347 #6 0x00007fa9cc42326e in _g_dbus_worker_emit_message_about_to_be_sent (message=0x55850cd44d40, worker=0x7fa9b800a2d0) at gdbusprivate.c:468 #7 continue_writing (worker=0x7fa9b800a2d0) at gdbusprivate.c:1459 #8 0x00007fa9cc42386f in write_message_cb (source_object=<optimized out>, res=<optimized out>, user_data=0x7fa9b4009b20) at gdbusprivate.c:1317 #9 0x00007fa9cc3e0534 in g_task_return_now (task=0x55850cafa5b0) at gtask.c:1145 #10 0x00007fa9cc3e0569 in complete_in_idle_cb (task=task@entry=0x55850cafa5b0) at gtask.c:1159 #11 0x00007fa9cbe38c27 in g_idle_dispatch (source=0x7fa9b4021390, callback=0x7fa9cc3e0560 <complete_in_idle_cb>, user_data=0x55850cafa5b0) at gmain.c:5586 #12 0x00007fa9cbe3c247 in g_main_dispatch (context=0x55850caf73a0) at gmain.c:3234
Let's see if this bug is fixed with the latest ibus in f25 or later. *** This bug has been marked as a duplicate of bug 1350291 ***