Bug 588676 - [abrt] crash in evolution-data-server-2.30.1-2.fc13: __strlen_sse2: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
[abrt] crash in evolution-data-server-2.30.1-2.fc13: __strlen_sse2: Process /...
Status: CLOSED DUPLICATE of bug 582890
Product: Fedora
Classification: Fedora
Component: evolution-data-server (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-05-04 05:10 EDT by piio
Modified: 2010-11-08 15:05 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-08 15:05:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (20.29 KB, text/plain)
2010-05-04 05:10 EDT, piio
no flags Details

  None (edit)
Description piio 2010-05-04 05:10:53 EDT
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/e-calendar-factory
component: evolution-data-server
crash_function: __strlen_sse2
executable: /usr/libexec/e-calendar-factory
global_uuid: ae3617ac84209dfba51e79f4461275e379b0c7c8
package: evolution-data-server-2.30.1-2.fc13
rating: 3
reason: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce: 1. Trying to check tasks and calendar appointments through clock applet
Comment 1 piio 2010-05-04 05:10:57 EDT
Created attachment 411226 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 15:05:34 EST

*** This bug has been marked as a duplicate of bug 582890 ***
Comment 3 Karel Klíč 2010-11-08 15:05:34 EST
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 #582890.

Sorry for the inconvenience.

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