Bug 590469 - [abrt] crash in evolution-2.30.1-3.fc13: _dbus_connection_lock: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.30.1-3.fc13: _dbus_connection_lock: Process /usr/...
Keywords:
Status: CLOSED DUPLICATE of bug 601843
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:880ba75be8c41883772337c42ae...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-09 17:29 UTC by Bostjan
Modified: 2010-11-09 15:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 15:21:10 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (28.93 KB, text/plain)
2010-05-09 17:29 UTC, Bostjan 		no flags Details
View All

Description Bostjan 2010-05-09 17:29:49 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: _dbus_connection_lock
executable: /usr/bin/evolution
global_uuid: 880ba75be8c41883772337c42ae4597e8bcf82da
kernel: 2.6.33.3-85.fc13.i686.PAE
package: evolution-2.30.1-3.fc13
rating: 3
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. At the time I was not actively using evolution, it was just sitting on one of the screens but still checking for new mail occasionally
2.
3.
Comment 1 Bostjan 2010-05-09 17:29:52 UTC 
Created attachment 412664 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 15:21:10 UTC 

*** This bug has been marked as a duplicate of bug 601843 ***
Comment 3 Karel Klíč 2010-11-09 15:21:10 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 #601843.

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