Bug 664183 - [abrt] evolution-2.32.1-1.fc14: has_case_prefix: Process /usr/libexec/evolution/2.32/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.1-1.fc14: has_case_prefix: Process /usr/libexec/evoluti...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5b118f63819dc6697fb80dd9f5a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-18 23:11 UTC by Dirk Foerster
Modified: 2010-12-20 08:41 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-20 08:41:08 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (17.08 KB, text/plain)
2010-12-18 23:11 UTC, Dirk Foerster 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 637641 0 None None None Never

Description Dirk Foerster 2010-12-18 23:11:04 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/evolution/2.32/evolution-alarm-notify
component: evolution
crash_function: has_case_prefix
executable: /usr/libexec/evolution/2.32/evolution-alarm-notify
kernel: 2.6.35.9-64.fc14.x86_64
package: evolution-2.32.1-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: 1292713200
uid: 500

How to reproduce
-----
1.Evolution was not started. Did not use Evolution.
2.
3.
Comment 1 Dirk Foerster 2010-12-18 23:11:09 UTC 
Created attachment 469553 [details]
File: backtrace
Comment 2 Milan Crha 2010-12-20 08:41:08 UTC 
Thanks for a bug report. The evolution-alarm-notification daemon was about to play an audio alarm set on one of your events, but it failed due to some memory issue.

I moved this upstream as [1]. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=637641
Note You need to log in before you can comment on or make changes to this bug.