Bug 695903 - [abrt] evolution-2.32.2-1.fc14: parse_value_from_blob: Process /usr/libexec/evolution/2.32/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.2-1.fc14: parse_value_from_blob: Process /usr/libexec/e...
Keywords:
Status: CLOSED DUPLICATE of bug 695901
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fcc5c545eb0eef5a882ec3d35c0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-12 21:50 UTC by David
Modified: 2011-04-13 06:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-13 06:33:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (66.65 KB, text/plain)
2011-04-12 21:51 UTC, David
no flags Details

Description David 2011-04-12 21:50:58 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 68254 bytes
cmdline: /usr/libexec/evolution/2.32/evolution-alarm-notify
component: evolution
Attached file: coredump, 11251712 bytes
crash_function: parse_value_from_blob
executable: /usr/libexec/evolution/2.32/evolution-alarm-notify
kernel: 2.6.35.12-88.fc14.i686
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: 1302638843
uid: 500

How to reproduce
-----
1.
2.
3.
unknown cause

Comment 1 David 2011-04-12 21:51:01 UTC
Created attachment 491604 [details]
File: backtrace

Comment 2 Milan Crha 2011-04-13 06:33:04 UTC
Thanks for a bug report. I suppose this is from the time of a crash reported in bug #695901, thus I'm marking this as a duplicate of it, though it's in a different process. I believe it's closely related.

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


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