Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 597679 - [abrt] crash in evolution-2.30.1-6.fc13: get_alignment: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.30.1-6.fc13: get_alignment: Process /usr/bin/evol...
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:52c8cb4d1468a56e095d51220b1...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-30 04:12 UTC by Mustafa Mehmed
Modified: 2011-06-27 17:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-06-27 17:04:11 UTC

Attachments (Terms of Use)
File: backtrace (deleted)
2010-05-30 04:12 UTC, Mustafa Mehmed
no flags Details

Description Mustafa Mehmed 2010-05-30 04:12:09 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: See bug # 597678 . Evolution restored all mail from previous step (see bug #597678), but not the contacts list. I attempted to restore from backup again in the hope that my contacts list would be restored as well, but it crashed again.
component: evolution
crash_function: get_alignment
executable: /usr/bin/evolution
global_uuid: 52c8cb4d1468a56e095d51220b169f05d9a55b00
package: evolution-2.30.1-6.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 Mustafa Mehmed 2010-05-30 04:12:17 UTC
Created attachment 417976 [details]
File: backtrace

Comment 2 Mustafa Mehmed 2010-05-30 04:23:36 UTC
Note that addressbook.db and addressbook.db.summary were restored to the correct location but cannot be read by evolution. The file type seems to be correct (Berkeley DB (Hash, version 9, native byte-order).

Comment 3 Mustafa Mehmed 2010-05-31 04:39:59 UTC
OK - cannot explain this. Shutdown machine overnight, restarted evolution today and all contacts have reappeared. No idea why.

Comment 4 Bug Zapper 2011-06-02 12:49:48 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here:

Comment 5 Bug Zapper 2011-06-27 17:04:11 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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