Bug 554390

Summary: [abrt] crash in evolution-2.28.2-1 magazine_chain_pop_head, update_node, em_utils_reply_to_message
Product: [Fedora] Fedora Reporter: Peter Hanecak <hany>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: chrys87, lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:5a15e82db64d8ddd953007170d3ffc2780afc15b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-01-13 14:18:10 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

Description Peter Hanecak 2010-01-11 15:59:29 UTC 
abrt 1.0.3 detected a crash.

How to reproduce
-----
1. lauch Evolution
2. hibernate computer
3. wake up computer
4. select email
5. reply to email
6. CRASH

Comment
-----
I've tried to reply to e-mail shortly after waking up computer from hibernation. After hibernation, apps gets "frozen" for a while (2-15 seconds, depending on application, ...) till stuff from swap is loaded into RAM I guess.

So, after clisking "reply" I got some swapping (2-3 seconds) then Evolution crashed.

Something did not get loaded on time?

Attached file: backtrace
cmdline: evolution
component: evolution
executable: /usr/bin/evolution
kernel: 2.6.31.9-174.fc12.x86_64
package: evolution-2.28.2-1.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
Comment 1 Peter Hanecak 2010-01-11 15:59:32 UTC 
Created attachment 383005 [details]
File: backtrace
Comment 2 Milan Crha 2010-01-13 14:18:10 UTC 
Thanks for a bug report. The attached backtrace is pretty similar to the one at bug #546375, though not exactly the same. I'm marking this as a duplicate, because I believe these are just other steps how to reproduce that bug.

*** This bug has been marked as a duplicate of bug 546375 ***