Version-Release number of selected component: ibus-1.5.10-1.fc22 Additional info: reporter: libreport-2.5.0 backtrace_rating: 4 cmdline: ibus-daemon --xim --panel disable crash_function: bus_dbus_impl_dispatch_message_by_rule executable: /usr/bin/ibus-daemon global_pid: 2180 kernel: 4.0.0-0.rc5.git4.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at lun. 2014-11-03 15:59:01 CET, end at jeu. 2015-04-02 09:55:22 CEST. -- Truncated backtrace: Thread no. 1 (10 frames) #4 bus_dbus_impl_dispatch_message_by_rule at dbusimpl.c:1901 #5 bus_dbus_impl_connection_filter_cb at dbusimpl.c:1578 #6 on_worker_message_about_to_be_sent at gdbusconnection.c:2429 #7 _g_dbus_worker_emit_message_about_to_be_sent at gdbusprivate.c:498 #8 continue_writing at gdbusprivate.c:1501 #9 write_message_cb at gdbusprivate.c:1356 #10 g_simple_async_result_complete at gsimpleasyncresult.c:763 #11 write_message_continue_writing at gdbusprivate.c:1070 #12 write_message_async at gdbusprivate.c:1136 #13 continue_writing at gdbusprivate.c:1541 Potential duplicate: bug 850539
Created attachment 1010047 [details] File: backtrace
Created attachment 1010048 [details] File: cgroup
Created attachment 1010049 [details] File: core_backtrace
Created attachment 1010050 [details] File: dso_list
Created attachment 1010051 [details] File: environ
Created attachment 1010052 [details] File: limits
Created attachment 1010053 [details] File: maps
Created attachment 1010054 [details] File: mountinfo
Created attachment 1010055 [details] File: namespaces
Created attachment 1010056 [details] File: open_fds
Created attachment 1010057 [details] File: proc_pid_status
I cannot reproduce your backtrace. Are you still able to reproduce your backtrace? (In reply to Maël Lavault from comment #1) > Created attachment 1010047 [details] > File: backtrace > #0 0x00007fbd82818a98 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 > #1 0x00007fbd8281a72a in __GI_abort () at abort.c:89 > #2 0x00007fbd82e30535 in g_assertion_message (domain=domain@entry=0x419286 "IBUS", file=file@entry=0x419746 "dbusimpl.c", line=line@entry=1901, func=func@entry=0x419ca0 <__func__.26193> "bus_dbus_impl_dispatch_message_by_rule", message=message@entry=0x7fbd7000a1f0 "assertion failed: (skip_connection == NULL || BUS_IS_CONNECTION (skip_connection))") at gtestutils.c:2356 > #3 0x00007fbd82e305ca in g_assertion_message_expr (domain=domain@entry=0x419286 "IBUS", file=file@entry=0x419746 "dbusimpl.c", line=line@entry=1901, func=func@entry=0x419ca0 <__func__.26193> "bus_dbus_impl_dispatch_message_by_rule", expr=expr@entry=0x419b20 "skip_connection == NULL || BUS_IS_CONNECTION (skip_connection)") at gtestutils.c:2371 > #4 0x0000000000409b9f in bus_dbus_impl_dispatch_message_by_rule (dbus=dbus@entry=0x228f830, message=message@entry=0x7fbd600050f0, skip_connection=skip_connection@entry=0x23d0930) at dbusimpl.c:1901 > #5 0x0000000000409f58 in bus_dbus_impl_connection_filter_cb (dbus_connection=<optimized out>, message=0x7fbd600050f0, incoming=<optimized out>, user_data=0x228f830) at dbusimpl.c:1578 > #6 0x00007fbd8341573f in on_worker_message_about_to_be_sent (worker=<optimized out>, message=0x22a1320, user_data=0x230ca40) at gdbusconnection.c:2429
No sorry I don't even know what have crashed. Abrt just popped up.
If you can reproduce your problem, please comment here again.