Bug 722374 - [abrt] evolution-2.32.2-1.fc14: has_case_prefix: Process /usr/libexec/evolution/2.32/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
[abrt] evolution-2.32.2-1.fc14: has_case_prefix: Process /usr/libexec/evoluti...
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2011-07-15 01:11 EDT by Shane Kerr
Modified: 2011-07-26 05:41 EDT (History)
3 users (show)

See Also:
Fixed In Version: evolution-3.0.0-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-07-26 05:41:17 EDT
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 (19.10 KB, text/plain)
2011-07-15 01:11 EDT, Shane Kerr
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 637641 None None None Never

  None (edit)
Description Shane Kerr 2011-07-15 01:11:01 EDT
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 19562 bytes
cmdline: /usr/libexec/evolution/2.32/evolution-alarm-notify
component: evolution
Attached file: coredump, 15257600 bytes
crash_function: has_case_prefix
executable: /usr/libexec/evolution/2.32/evolution-alarm-notify
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: 1310706482
uid: 500

How to reproduce
1. Started computer.
2. ?
3. Profit!
Comment 1 Shane Kerr 2011-07-15 01:11:04 EDT
Created attachment 513321 [details]
File: backtrace
Comment 2 Milan Crha 2011-07-26 05:41:17 EDT
Thanks for a bug report. This was fixed within upstream bug report [1]. The fix is included in the current stable release of Evolution, and is part of evolution-3.0.0-1 too.

[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.