Red Hat Bugzilla – Bug 1026610
[abrt] evolution-3.8.5-2.fc19: gtk_container_propagate_draw: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Last modified: 2015-02-17 14:03:50 EST
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 gtk_container_propagate_draw at gtkcontainer.c:3322
#1 gtk_box_forall at gtkbox.c:1865
#2 gtk_container_draw at gtkcontainer.c:3239
#3 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:130
#4 gtk_widget_draw_marshallerv at gtkwidget.c:906
#5 _g_closure_invoke_va at gclosure.c:840
#8 _gtk_widget_draw_internal at gtkwidget.c:6173
#9 gtk_container_propagate_draw at gtkcontainer.c:3375
#10 gtk_box_forall at gtkbox.c:1865
#11 gtk_container_draw at gtkcontainer.c:3239
Created attachment 819498 [details]
Created attachment 819499 [details]
Created attachment 819500 [details]
Created attachment 819501 [details]
Created attachment 819502 [details]
Created attachment 819503 [details]
Created attachment 819504 [details]
Created attachment 819505 [details]
Created attachment 819506 [details]
Created attachment 819507 [details]
Created attachment 819508 [details]
Thanks for a bug report. I do not see why the crash happened in the backtrace, only where it did that. I guess it might be caused by some use-after-free of a memory. By any chance, do you have any steps to reproduce this please?
I haven't been able to reproduce it reliably. It happens on startup sometimes. Evo also seems to just crash randomly at times. I'm beginning to suspect it might have to do with the fact that I have multiple instances of mail readers pointing at the same Exchange account. Last time I noticed an evo crash, it followed viewing mail in the Exchange account on my phone. Maybe it has to do with updating the status of the Exchange account if it's different from what's cached?
Just speculating at this point.
So the following just happened: I read a message on my phone, then hit send/receive on evo, and evo crashed.
A data point supporting my speculation.
Was the backtrace any similar to the one from above, or completely different? If you can, please give me the backtrace of the reproduced crash.
Abrt seems to file these on a whim. I'm not sure how to grab the traceback, but Abrt has filed or added to several bugs as it has misbehaved. If you search for Abrt submissions for evolution, goa, and something else I can't recall right now (mission-control, maybe?), from me, you should find several backtraces that might help.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.