Bug 692952

Summary: [abrt] evolution-2.32.2-1.fc14: remove_queued_alarm: Process /usr/libexec/evolution/2.32/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: bwbees0
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:26a28634c915cea96238b489ceb3e9ce6e441a91
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-04 10:11:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description bwbees0 2011-04-01 19:08:17 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 31290 bytes
cmdline: /usr/libexec/evolution/2.32/evolution-alarm-notify
comment: See above.
component: evolution
Attached file: coredump, 14888960 bytes
crash_function: remove_queued_alarm
executable: /usr/libexec/evolution/2.32/evolution-alarm-notify
kernel: 2.6.35.11-83.fc14.x86_64
package: evolution-2.32.2-1.fc14
rating: 4
reason: Process /usr/libexec/evolution/2.32/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301683577
uid: 500

How to reproduce
-----
1. I was composing an email that was forwarded from an already received email.
2. I attempted to open the calendar tab in Evolution to check a date.
3. The application froze for a few minutes and a crash alert was generated.
Comment 1 bwbees0 2011-04-01 19:08:19 UTC 
Created attachment 489447 [details]
File: backtrace
Comment 2 Milan Crha 2011-04-04 10:11:44 UTC 
Thanks for a bug report. There had been reported a similar bug report already, thus I'm marking it as a duplicate.

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