Bug 616782 - [abrt] crash in evolution-2.30.2-1.fc13: __libc_free: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.30.2-1.fc13: __libc_free: Process /usr/bin/evolut...
Keywords:
Status: CLOSED DUPLICATE of bug 615370
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a66a699c862f8c409b9ff4dbfe9...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-21 12:18 UTC by Sanford Darlington
Modified: 2010-11-08 18:50 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-08 18:50:57 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (37.94 KB, text/plain)
2010-07-21 12:18 UTC, Sanford Darlington 		no flags Details
View All

Description Sanford Darlington 2010-07-21 12:18:10 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: Ongoing problem with this version of openldap.  I'll downgrade it and it should work again.
component: evolution
crash_function: __libc_free
executable: /usr/bin/evolution
global_uuid: a66a699c862f8c409b9ff4dbfe91edd5bab4c797
kernel: 2.6.33.6-147.fc13.x86_64
package: evolution-2.30.2-1.fc13
rating: 3
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Took the update for today (7/21/2010) which also update openldap to -9.
2. Started Evolution.
3. Crash!
Comment 1 Sanford Darlington 2010-07-21 12:18:12 UTC 
Created attachment 433398 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 18:50:57 UTC 

*** This bug has been marked as a duplicate of bug 615370 ***
Comment 3 Karel Klíč 2010-11-08 18:50:57 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #615370.

Sorry for the inconvenience.
Note You need to log in before you can comment on or make changes to this bug.