Bug 696529 - [abrt] evolution-data-server-2.32.2-1.fc14: _dbus_watch_invalidate: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-data-server-2.32.2-1.fc14: _dbus_watch_invalidate: Process /...
Keywords:
Status: CLOSED DUPLICATE of bug 696285
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:99e0d91a9ed54d34e0b4b3b838e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-14 08:47 UTC by Herald van der Breggen
Modified: 2011-04-14 11:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-14 11:57:03 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (18.71 KB, text/plain)
2011-04-14 08:47 UTC, Herald van der Breggen
no flags Details

Description Herald van der Breggen 2011-04-14 08:47:41 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 19157 bytes
cmdline: /usr/libexec/e-addressbook-factory
comment: it is really a matter of login in. Maybe older data in the home directory is related (upgraded from f13)
component: evolution-data-server
Attached file: coredump, 27656192 bytes
crash_function: _dbus_watch_invalidate
executable: /usr/libexec/e-addressbook-factory
kernel: 2.6.35.12-88.fc14.x86_64
package: evolution-data-server-2.32.2-1.fc14
rating: 4
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1302770727
uid: 500

How to reproduce
-----
1. login
2.
3.

Comment 1 Herald van der Breggen 2011-04-14 08:47:44 UTC
Created attachment 491998 [details]
File: backtrace

Comment 2 Milan Crha 2011-04-14 11:57:03 UTC
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate.

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


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