Bug 595254 - [abrt] crash in evolution-2.30.1-5.fc13: is_online: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.30.1-5.fc13: is_online: Process /usr/bin/evolutio...
Status: CLOSED DUPLICATE of bug 594524
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b05dbe2634609e4f8cf5fa1f6f7...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-24 08:17 UTC by Oded Arbel
Modified: 2010-05-25 08:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 08:23:37 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (72.08 KB, text/plain)
2010-05-24 08:17 UTC, Oded Arbel 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Oded Arbel 2010-05-24 08:17:38 UTC 
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/evolution
component: evolution
crash_function: is_online
executable: /usr/bin/evolution
global_uuid: b05dbe2634609e4f8cf5fa1f6f7ec4dcb1d45c08
kernel: 2.6.33.3-79.fc13.x86_64
package: evolution-2.30.1-5.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Oded Arbel 2010-05-24 08:17:40 UTC 
Created attachment 416051 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 08:23:37 UTC 

*** This bug has been marked as a duplicate of bug 594524 ***
Comment 3 Karel Klíč 2010-05-25 08:23:37 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 #594524.

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