Bug 1026610

Summary: [abrt] evolution-3.8.5-2.fc19: gtk_container_propagate_draw: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Matthew Saltzman <mjs>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: alex.go4more, lucilanga, mbarnes, mcrha, mjs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/1b4366e1235a4ab98169b7c98f7561b99e2424b9
Whiteboard: abrt_hash:a5b72839853fb7078503c0cde98341e85ac0053c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 19:03:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Matthew Saltzman 2013-11-05 04:02:59 UTC
Version-Release number of selected component:
evolution-3.8.5-2.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        evolution
crash_function: gtk_container_propagate_draw
executable:     /usr/bin/evolution
kernel:         3.11.6-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
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

Comment 1 Matthew Saltzman 2013-11-05 04:03:08 UTC
Created attachment 819498 [details]
File: backtrace

Comment 2 Matthew Saltzman 2013-11-05 04:03:11 UTC
Created attachment 819499 [details]
File: cgroup

Comment 3 Matthew Saltzman 2013-11-05 04:03:16 UTC
Created attachment 819500 [details]
File: core_backtrace

Comment 4 Matthew Saltzman 2013-11-05 04:03:20 UTC
Created attachment 819501 [details]
File: dso_list

Comment 5 Matthew Saltzman 2013-11-05 04:03:23 UTC
Created attachment 819502 [details]
File: environ

Comment 6 Matthew Saltzman 2013-11-05 04:03:26 UTC
Created attachment 819503 [details]
File: exploitable

Comment 7 Matthew Saltzman 2013-11-05 04:03:29 UTC
Created attachment 819504 [details]
File: limits

Comment 8 Matthew Saltzman 2013-11-05 04:03:34 UTC
Created attachment 819505 [details]
File: maps

Comment 9 Matthew Saltzman 2013-11-05 04:03:38 UTC
Created attachment 819506 [details]
File: open_fds

Comment 10 Matthew Saltzman 2013-11-05 04:03:41 UTC
Created attachment 819507 [details]
File: proc_pid_status

Comment 11 Matthew Saltzman 2013-11-05 04:03:44 UTC
Created attachment 819508 [details]
File: var_log_messages

Comment 12 Milan Crha 2013-11-05 17:26:58 UTC
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?

Comment 13 Matthew Saltzman 2013-11-06 17:32:31 UTC
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.

Comment 14 Matthew Saltzman 2013-11-06 17:42:49 UTC
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.

Comment 15 Milan Crha 2013-11-08 13:08:56 UTC
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.

Comment 16 Matthew Saltzman 2013-11-09 21:24:44 UTC
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.

Comment 17 Fedora Admin XMLRPC Client 2014-09-04 14:29:20 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 18 Fedora End Of Life 2015-01-09 20:28:19 UTC
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.

Comment 19 Fedora End Of Life 2015-02-17 19:03:50 UTC
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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.