Bug 627329 - [abrt] evolution-2.30.2-4.fc13: remove_queued_alarm: Process /usr/libexec/evolution/2.30/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
[abrt] evolution-2.30.2-4.fc13: remove_queued_alarm: Process /usr/libexec/evo...
Status: CLOSED DUPLICATE of bug 614986
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-08-25 13:18 EDT by Adam Carbone
Modified: 2010-11-09 10:34 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 10:34:16 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 (29.25 KB, text/plain)
2010-08-25 13:18 EDT, Adam Carbone
no flags Details

  None (edit)
Description Adam Carbone 2010-08-25 13:18:09 EDT
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/evolution/2.30/evolution-alarm-notify
component: evolution
crash_function: remove_queued_alarm
executable: /usr/libexec/evolution/2.30/evolution-alarm-notify
package: evolution-2.30.2-4.fc13
rating: 4
reason: Process /usr/libexec/evolution/2.30/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1282756519
uid: 500

How to reproduce
1.clicked to dismiss notification from panel
Comment 1 Adam Carbone 2010-08-25 13:18:11 EDT
Created an attachment (id=441003)
File: backtrace
Comment 2 Karel Klíč 2010-11-09 10:34:16 EST

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

Sorry for the inconvenience.

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