Bug 628002 - [abrt] evolution-2.30.2-4.fc13: raise: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Summary: [abrt] evolution-2.30.2-4.fc13: raise: Process /usr/bin/evolution was killed ...
Keywords:
Status: CLOSED DUPLICATE of bug 604260
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:370c90a61b1cd2562bdf46bfade...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-27 16:07 UTC by Muel Kiel
Modified: 2010-11-08 19:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 19:56:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (52.85 KB, text/plain)
2010-08-27 16:07 UTC, Muel Kiel
no flags Details

Description Muel Kiel 2010-08-27 16:07:03 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: I think it had something to do with accessing the calendar from both the web interface and evolution at the same time on the same computer.
component: evolution
crash_function: raise
executable: /usr/bin/evolution
kernel: 2.6.33.8-149.fc13.x86_64
package: evolution-2.30.2-4.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1282923973
uid: 500

How to reproduce
-----
1. I had just added events to a google calendar from Evolution
2. I went to google.com/calendar to see if they had been updated on the site
3. They hadn't been updated 
4. I hit refresh on the calendar right click pop up
5. I refreshed the google calendar site
6. Evolution crashed

Comment 1 Muel Kiel 2010-08-27 16:07:05 UTC
Created an attachment (id=441550)
File: backtrace

Comment 2 Karel Klíč 2010-11-08 19:56:25 UTC

*** This bug has been marked as a duplicate of bug 604260 ***

Comment 3 Karel Klíč 2010-11-08 19:56:25 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 #604260.

Sorry for the inconvenience.


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