Bug 693714 - [abrt] evolution-2.32.2-1.fc14: vasprintf: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.2-1.fc14: vasprintf: Process /usr/bin/evolution was kil...
Keywords:
Status: CLOSED DUPLICATE of bug 650338
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:66a31f1365076fa270a17036933...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-05 12:05 UTC by Gianluca Cecchi
Modified: 2011-04-06 06:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-06 06:32:28 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (107.51 KB, text/plain)
2011-04-05 12:05 UTC, Gianluca Cecchi 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Gianluca Cecchi 2011-04-05 12:05:34 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 110088 bytes
cmdline: evolution
comment: It is about three times in the latest week that this happens...
component: evolution
Attached file: coredump, 570077184 bytes
crash_function: vasprintf
executable: /usr/bin/evolution
kernel: 2.6.35.11-83.fc14.x86_64
package: evolution-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1302001761
uid: 500

How to reproduce
-----
1. evolution was open
2. coming back from lunch I see evolution no more in execution
3. I see abrt icon showing segv message for evolution
Comment 1 Gianluca Cecchi 2011-04-05 12:05:36 UTC 
Created attachment 489970 [details]
File: backtrace
Comment 2 Milan Crha 2011-04-06 06:32:28 UTC 
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate.

*** This bug has been marked as a duplicate of bug 650338 ***
Note You need to log in before you can comment on or make changes to this bug.