Hide Forgot
Version-Release number of selected component: ibus-1.5.11-1.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: ibus-daemon --xim --panel disable crash_function: bus_dbus_impl_connection_filter_cb executable: /usr/bin/ibus-daemon global_pid: 1920 kernel: 4.4.3-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #4 bus_dbus_impl_connection_filter_cb at dbusimpl.c:1473 #5 on_worker_message_about_to_be_sent at gdbusconnection.c:2343 #6 _g_dbus_worker_emit_message_about_to_be_sent at gdbusprivate.c:465 #7 continue_writing at gdbusprivate.c:1455 #8 write_message_cb at gdbusprivate.c:1313 #9 g_task_return_now at gtask.c:1106 #10 complete_in_idle_cb at gtask.c:1120 #15 gdbus_shared_thread_func at gdbusprivate.c:246 #16 g_thread_proxy at gthread.c:778 Potential duplicate: bug 906086
Created attachment 1133790 [details] File: backtrace
Created attachment 1133791 [details] File: cgroup
Created attachment 1133792 [details] File: core_backtrace
Created attachment 1133793 [details] File: dso_list
Created attachment 1133794 [details] File: environ
Created attachment 1133795 [details] File: limits
Created attachment 1133796 [details] File: maps
Created attachment 1133797 [details] File: mountinfo
Created attachment 1133798 [details] File: namespaces
Created attachment 1133799 [details] File: open_fds
Created attachment 1133800 [details] File: proc_pid_status
Created attachment 1133801 [details] File: var_log_messages
I cannot reproduce your backtrace. Are you still able to reproduce your backtrace? (In reply to rat from comment #1) > Created attachment 1133790 [details] > File: backtrace #0 0x00007f4847f38a98 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x00007f4847f3a69a in __GI_abort () at abort.c:89 #2 0x00007f48485519e5 in g_assertion_message (domain=domain@entry=0x55d42b175b3a "IBUS", file=file@entry=0x55d42b175fe6 "dbusimpl.c", line=line@entry=1473, func=func@entry=0x55d42b176620 <__func__.26086> "bus_dbus_impl_connection_filter_cb", message=message@entry=0x7f483000fa00 "assertion failed: (connection != NULL)") at gtestutils.c:2429 #3 0x00007f4848551a7a in g_assertion_message_expr (domain=domain@entry=0x55d42b175b3a "IBUS", file=file@entry=0x55d42b175fe6 "dbusimpl.c", line=line@entry=1473, func=func@entry=0x55d42b176620 <__func__.26086> "bus_dbus_impl_connection_filter_cb", expr=expr@entry=0x55d42b175ff1 "connection != NULL") at gtestutils.c:2444 #4 0x000055d42b165c56 in bus_dbus_impl_connection_filter_cb (dbus_connection=<optimized out>, message=0x55d42d095f20, incoming=0, user_data=0x55d42d083830) at dbusimpl.c:1473 #5 0x00007f4848b393ee in on_worker_message_about_to_be_sent (worker=<optimized out>, message=0x55d42d095f20, user_data=0x7f4834007320) at gdbusconnection.c:2343 #6 0x00007f4848b4ea75 in _g_dbus_worker_emit_message_about_to_be_sent (message=0x55d42d095f20, worker=0x7f4834005f20) at gdbusprivate.c:465 #7 continue_writing (worker=0x7f4834005f20) at gdbusprivate.c:1455 #8 0x00007f4848b4f02f in write_message_cb (source_object=<optimized out>, res=<optimized out>, user_data=0x55d42d1fb8c0) at gdbusprivate.c:1313 #9 0x00007f4848af25a3 in g_task_return_now (task=0x7f4830002ac0) at gtask.c:1106 #10 0x00007f4848af25d9 in complete_in_idle_cb (task=0x7f4830002ac0) at gtask.c:1120 #11 0x00007f484852be3a in g_main_dispatch (context=0x55d42d102b50) at gmain.c:3154
(In reply to fujiwara from comment #13) > I cannot reproduce your backtrace. > Are you still able to reproduce your backtrace? > Hi, I am sorry, but I don't know how to reproduce the backtrace. I am not technically sound. If you meant to ask if I could reproduce the issue, the answer is no. Honestly I just submitted because it showed up in problem reporting tool. But If there is anything I can do to provide more info, I am happy to help.
(In reply to rat from comment #14) > (In reply to fujiwara from comment #13) > > I cannot reproduce your backtrace. > > Are you still able to reproduce your backtrace? > > > Hi, I am sorry, but I don't know how to reproduce the backtrace. > I am not technically sound. When you filed this issue with abrt, abrt retrieved the backtrace and you could check it on GUI before you actually submit it. > > If you meant to ask if I could reproduce the issue, the answer is no. > Honestly I just submitted because it showed up in problem reporting tool. > But If there is anything I can do to provide more info, I am happy to help. If you will reproduce your backtrace again, please comment here.
*** Bug 1331678 has been marked as a duplicate of this bug. ***
*** Bug 1337508 has been marked as a duplicate of this bug. ***