Red Hat Bugzilla – Bug 1006091
[abrt] evolution-3.8.5-2.fc19: _gdk_x11_display_error_event: Process /usr/bin/evolution was killed by signal 5 (SIGTRAP)
Last modified: 2013-09-11 03:56:45 EDT
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#2 _gdk_x11_display_error_event at gdkdisplay-x11.c:2556
#5 handle_error at xcb_io.c:213
#6 handle_response at xcb_io.c:325
#9 _gdk_x11_display_send_xevent at gdkmain-x11.c:359
#10 _gdk_x11_display_send_selection_notify at gdkselection-x11.c:329
#11 _gtk_selection_request at gtkselection.c:2514
#12 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:130
#13 _g_closure_invoke_va at gclosure.c:840
#16 gtk_widget_event_internal at gtkwidget.c:6714
#17 gtk_widget_event at gtkwidget.c:6371
Potential duplicate: bug 902115
Created attachment 795787 [details]
Created attachment 795788 [details]
Created attachment 795789 [details]
Created attachment 795790 [details]
Created attachment 795791 [details]
Created attachment 795792 [details]
Created attachment 795793 [details]
Created attachment 795794 [details]
Created attachment 795795 [details]
Created attachment 795796 [details]
Thanks for a bug report. I do not see from the backtrace what exactly caused the crash, there is only partial message shown, which is printed on evolution's console:
The program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 456753 error_code 3 req"...
By any chance, are you able to reproduce this with certain steps, please?
No, It just happened for the first time with this report. I use Gnome 3.8.4-2.fc19.x86_64. I had Evolution and Firefox open in one virtual desktop and was using Edit and Terminal in another virtual desktop. As I recall I received a notification of new mail and then almost immediately afterwards a notification from Automatic Bug Reporting Tool of the error in Evolution. So I was not directly interacting with Evolution, in fact it was not displayed, at the time of the error. I do not know how I would reproduce the error.
Thanks for the update. Maybe just a temporary failure in some function, who knows. I would close this for now, but please feel free to update this bug report if you find anything in the future. Thanks in advance.