Description of problem: I'm not sure why the program crashed. The computer had been sleeping and I woke it up with an HDMI cable attached ready for a presentation. Version-Release number of selected component: ibus-1.5.6-1.fc19 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/libexec/ibus-x11 --kill-daemon crash_function: ffi_call_unix64 executable: /usr/libexec/ibus-x11 kernel: 3.13.9-100.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #5 ffi_call_unix64 at ../src/x86/unix64.S:76 #6 ffi_call at ../src/x86/ffi64.c:522 #7 g_cclosure_marshal_generic_va at gclosure.c:1550 #8 _g_closure_invoke_va at gclosure.c:840 #11 emit_closed_in_idle at gdbusconnection.c:1377 #16 gtk_main at gtkmain.c:1257
Created attachment 886146 [details] File: backtrace
Created attachment 886147 [details] File: cgroup
Created attachment 886148 [details] File: core_backtrace
Created attachment 886149 [details] File: dso_list
Created attachment 886150 [details] File: environ
Created attachment 886151 [details] File: exploitable
Created attachment 886152 [details] File: limits
Created attachment 886153 [details] File: maps
Created attachment 886154 [details] File: open_fds
Created attachment 886155 [details] File: proc_pid_status
Created attachment 886156 [details] File: var_log_messages
I cannot reproduce your backtrace. Are you still able to reproduce your backtrace? (In reply to mkwadee from comment #1) > Created attachment 886146 [details] > File: backtrace > #0 __run_exit_handlers (status=status@entry=1, listp=0x3f693ba6e8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:49 > #1 0x0000003f690392c5 in __GI_exit (status=status@entry=1) at exit.c:99 > #2 0x000000000040377e in _sighandler (sig=<optimized out>) at main.c:1103 > #3 <signal handler called> > #4 0x0000003f69c0ee6b in raise (sig=15) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37 > #5 0x0000003f6d405cfc in ffi_call_unix64 () at ../src/x86/unix64.S:76 > #6 0x0000003f6d40562c in ffi_call (cif=cif@entry=0x7fffd9d58550, fn=0x3af48b49c0 <g_dbus_connection_real_closed>, rvalue=0x7fffd9d58480, avalue=avalue@entry=0x7fffd9d58420) at ../src/x86/ffi64.c:522 > #7 0x0000003af3c106c5 in g_cclosure_marshal_generic_va (closure=0x25ff880, return_value=0x0, instance=0x2602030, args_list=<optimized out>, marshal_data=0x3af48b49c0 <g_dbus_connection_real_closed>, n_params=2, param_types=0x25ff8f0) at gclosure.c:1550 > #8 0x0000003af3c0fc57 in _g_closure_invoke_va (closure=closure@entry=0x25ff880, return_value=return_value@entry=0x0, instance=instance@entry=0x2602030, args=args@entry=0x7fffd9d58798, n_params=2, param_types=0x25ff8f0) at gclosure.c:840 > #9 0x0000003af3c27d4d in g_signal_emit_valist (instance=0x2602030, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fffd9d58798) at gsignal.c:3234 > #10 0x0000003af3c28a32 in g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=detail@entry=0) at gsignal.c:3384 0x7fffd9d58870, reg_save_area = 0x7fffd9d587b0}} > #11 0x0000003af48b3755 in emit_closed_in_idle (user_data=0x7ff4180073c0) at gdbusconnection.c:1377 > #12 0x0000003af3847dc6 in g_main_dispatch (context=0x25f0b60) at gmain.c:3054
The problem has not occurred again with this particular version. A new version has been installed in the last update.
If you are still able to reproduce your problem, please comment here.