Bug 587392

Summary: [abrt] crash in evolution-2.28.3-1.fc12: Process /usr/libexec/evolution/2.28/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Egon Kastelijn <redhat2>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: aamuuninen, lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:2deff9290cbc8a37c13f12d552e0dbe273e5ad03
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-22 11:55:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Egon Kastelijn 2010-04-29 19:27:36 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/evolution/2.28/evolution-alarm-notify --oaf-activate-iid=OAFIID:GNOME_Evolution_Calendar_AlarmNotify_Factory:2.28 --oaf-ior-fd=20
component: evolution
executable: /usr/libexec/evolution/2.28/evolution-alarm-notify
global_uuid: 2deff9290cbc8a37c13f12d552e0dbe273e5ad03
kernel: 2.6.32.11-99.fc12.x86_64
package: evolution-2.28.3-1.fc12
rating: 4
reason: Process /usr/libexec/evolution/2.28/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. I don't know what caused this.
2.
3.
Comment 1 Egon Kastelijn 2010-04-29 19:27:38 UTC 
Created attachment 410209 [details]
File: backtrace
Comment 2 William Glover 2010-05-22 11:55:49 UTC 

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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