|Summary:||[abrt] crash in exaile-0.3.1.1-1.fc12: raise: Process /usr/bin/python was killed by signal 6 (SIGABRT)|
|Product:||[Fedora] Fedora||Reporter:||Julian <devlists>|
|Component:||exaile||Assignee:||Deji Akingunola <dakingun>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2010-12-03 14:23:58 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Julian 2010-05-25 11:28:34 UTC
abrt 1.0.9 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: python /usr/lib/python2.6/site-packages/exaile/exaile.py --datadir=/usr/share/exaile/data --startgui component: exaile crash_function: raise executable: /usr/bin/python global_uuid: 764f96e920eb04b174716a986f45c55d545b6363 kernel: 22.214.171.124-115.fc12.x86_64 package: exaile-0.3.1.1-1.fc12 rating: 4 reason: Process /usr/bin/python was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine) comment ----- cant say for sure if it quits at the end of one song or when opening the next. there are no broken references in the playlist, all files exists and can be played (have been in fact) by exaile. so this happens after some random song and not after / befor a specific one. thanks for looking into this! How to reproduce ----- 1. run exaile in background 2. play some music 3. exaile crashes after some time, right after a song.
Comment 2 Fedora Update System 2010-06-29 16:34:56 UTC
exaile-0.3.2.0-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/exaile-0.3.2.0-1.fc12
Comment 3 Fedora Update System 2010-06-30 15:15:29 UTC
exaile-0.3.2.0-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update exaile'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/exaile-0.3.2.0-1.fc12
Comment 4 Bug Zapper 2010-11-03 14:15:24 UTC
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 5 Julian 2010-11-03 16:43:53 UTC
completely forgot about this one, but i already moved on to f14 and even in f13 the bug didnt exists for me anymore. thx!
Comment 6 Bug Zapper 2010-12-03 14:23:58 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.