Bug 598336 - [abrt] crash in picard-0.12.1-1.fc13: raise: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in picard-0.12.1-1.fc13: raise: Process /usr/bin/python was kill...
Alias: None
Product: Fedora
Classification: Fedora
Component: picard   
(Show other bugs)
Version: 13
Hardware: i686 Linux
Target Milestone: ---
Assignee: Alex Lancaster
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:dca86d54b980ffb91b561174414...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-01 06:18 UTC by Matt Lee
Modified: 2011-06-27 17:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-27 17:13:43 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 (104.48 KB, text/plain)
2010-06-01 06:18 UTC, Matt Lee
no flags Details

Description Matt Lee 2010-06-01 06:18:37 UTC
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/picard
comment: I have used Picard in the past (F11) and it didn't crash. This crash seem to happen under F13.
component: picard
crash_function: raise
executable: /usr/bin/python
global_uuid: dca86d54b980ffb91b561174414f00745bb3c87a
package: picard-0.12.1-1.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
1. Start picard.
2. Add a folder with about 7000 files into Picard.
3. Picard crashes

Comment 1 Matt Lee 2010-06-01 06:18:38 UTC
Created attachment 418487 [details]
File: backtrace

Comment 2 Alex Lancaster 2010-08-25 06:49:33 UTC
Can you generate a reproducible test-case? or perhaps narrow down the crash to a particular file?  It's difficult to debug without being able to reliably reproduce.

Comment 3 Bug Zapper 2011-06-02 12:32:47 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 Bug Zapper 2011-06-27 17:13:43 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.