Red Hat Bugzilla – Bug 1250638
[abrt] Crash under captured_event_cb at gtkscrolledwindow.c:1152
Last modified: 2016-07-19 13:22:13 EDT
Description of problem:
Laptop had just come out of sleep. I had just clicked on the title banner to bring Evolution into the foreground.
I expect the mail server had timed out the IMAP TCP connection which the local evolution side had not. My guess is that Evolution was unable to handle the dropped tcp connection.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (9 frames)
#0 strstr at strstr.c:63
#1 captured_event_cb at gtkscrolledwindow.c:1152
#2 _gtk_widget_captured_event at gtkwidget.c:7482
#3 propagate_event_down at gtkmain.c:2472
#4 propagate_event at gtkmain.c:2520
#5 _gtk_propagate_captured_event at gtkmain.c:2563
#6 gtk_main_do_event at gtkmain.c:1750
#7 _gdk_event_emit at gdkevents.c:69
#13 gtk_main at gtkmain.c:1219
Created attachment 1059542 [details]
Created attachment 1059543 [details]
Created attachment 1059544 [details]
Created attachment 1059545 [details]
Created attachment 1059546 [details]
Created attachment 1059547 [details]
Created attachment 1059548 [details]
Created attachment 1059549 [details]
Created attachment 1059550 [details]
Created attachment 1059551 [details]
Created attachment 1059552 [details]
Created attachment 1059553 [details]
Thanks for a bug report. The backtrace shows the crash in the gtk+ code, when processing a mouse click (or some such mouse event). There is almost none code related to the evolution (the only is the main() function), thus I move this to the gtk3 package.
The only evolution involvement would be in case of some kind of a memory corruption, like some part of the code accessing already freed memory, but it doesn't seem to be the case here, at least on the first look.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.