Bug 554390 - [abrt] crash in evolution-2.28.2-1 magazine_chain_pop_head, update_node, em_utils_reply_to_message
Summary: [abrt] crash in evolution-2.28.2-1 magazine_chain_pop_head, update_node, em_u...
Keywords:
Status: CLOSED DUPLICATE of bug 546375
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5a15e82db64d8ddd953007170d3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-11 15:59 UTC by Peter Hanecak
Modified: 2010-02-25 21:10 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-01-13 14:18:10 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (66.34 KB, text/plain)
2010-01-11 15:59 UTC, Peter Hanecak 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.