Bug 602503 - [abrt] crash in evolution-data-server-2.30.1-2.fc13: get_cal_address: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-data-server-2.30.1-2.fc13: get_cal_address: Process...
Keywords:
Status: CLOSED DUPLICATE of bug 598747
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5b479354fd86e12da615f70e530...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-10 02:02 UTC by Vladimir Mencl
Modified: 2010-11-09 15:28 UTC (History)
2 users (show)

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

Attachments (Terms of Use)
File: backtrace (18.46 KB, text/plain)
2010-06-10 02:03 UTC, Vladimir Mencl 		no flags Details
View All

Description Vladimir Mencl 2010-06-10 02:02:59 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/e-calendar-factory
comment: tried to make an appointment in a shared exchange calendar
component: evolution-data-server
crash_function: get_cal_address
executable: /usr/libexec/e-calendar-factory
global_uuid: 5b479354fd86e12da615f70e530eb2efb3e2f1bb
kernel: 2.6.33.5-112.fc13.i686
package: evolution-data-server-2.30.1-2.fc13
rating: 4
reason: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Vladimir Mencl 2010-06-10 02:03:01 UTC 
Created attachment 422745 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 15:28:15 UTC 

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

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