Bug 626376 - [abrt] evolution-2.30.2-4.fc13: g_hash_table_lookup_node: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.30.2-4.fc13: g_hash_table_lookup_node: Process /usr/bin/ev...
Status: CLOSED DUPLICATE of bug 629779
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
(Show other bugs)
Version: 13
Hardware: x86_64 Linux
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:373d49ea221463e45f40f1b7ad9...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-23 12:05 UTC by Matthew Saltzman
Modified: 2010-11-09 13:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 13:54:12 UTC
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 (59.09 KB, text/plain)
2010-08-23 12:05 UTC, Matthew Saltzman
no flags Details

Description Matthew Saltzman 2010-08-23 12:05:29 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: Crash occurred on startup.  Seems to be related to having an OWA Echange account.
component: evolution
crash_function: g_hash_table_lookup_node
executable: /usr/bin/evolution
package: evolution-2.30.2-4.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1282564913
uid: 500

Comment 1 Matthew Saltzman 2010-08-23 12:05:32 UTC
Created an attachment (id=440366)
File: backtrace

Comment 2 Karel Klíč 2010-11-09 13:54:12 UTC

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

Comment 3 Karel Klíč 2010-11-09 13:54:12 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #629779.

Sorry for the inconvenience.

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