Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 596310 - [abrt] crash in offlineimap-6.1.2-2.fc12: raise: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in offlineimap-6.1.2-2.fc12: raise: Process /usr/bin/python was ...
Alias: None
Product: Fedora
Classification: Fedora
Component: offlineimap
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Christoph Höger
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:a67e1f3d60164604e97342a669b...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-26 15:03 UTC by J.H.M. Dassen (Ray)
Modified: 2013-07-03 04:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-06-27 16:42:50 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (145.24 KB, text/plain)
2010-05-26 15:03 UTC, J.H.M. Dassen (Ray)
no flags Details

Description J.H.M. Dassen (Ray) 2010-05-26 15:03:37 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/offlineimap
component: offlineimap
crash_function: raise
executable: /usr/bin/python
global_uuid: a67e1f3d60164604e97342a669bb1aeb235da100
package: offlineimap-6.1.2-2.fc12
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
How to reproduce: No reproducer known; first occurance of this issue.

What I did:
1. Did a full system reinstall with Fedora 13 (was running Fedora 12 previously).
2. Restored offlineimap configuration and folders from backup.
3. Installed python-kerberos to have offlineimap use Kerberos tickets.
4. Had offlineimap run for some hours against an IMAPS service.

Comment 1 J.H.M. Dassen (Ray) 2010-05-26 15:03:50 UTC
Created attachment 416873 [details]
File: backtrace

Comment 2 Anthony Green 2010-05-31 12:23:36 UTC
Package: offlineimap-6.1.2-2.fc12
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)

I was downloading from a remote IMAP to a local maildir repository.

Comment 3 Bug Zapper 2011-06-02 13:24:52 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 4 J.H.M. Dassen (Ray) 2011-06-02 16:21:57 UTC
I have not encountered this issue so far since updating to Fedora 15.

Comment 5 Bug Zapper 2011-06-27 16:42:50 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.