abrt version: 1.1.13 architecture: i686 Attached file: backtrace cmdline: python /usr/lib/python2.7/site-packages/exaile/exaile.py --datadir=/usr/share/exaile/data --startgui component: exaile crash_function: raise executable: /usr/bin/python kernel: 2.6.35.6-48.fc14.i686 package: exaile-0.3.2.0-2.fc14 rating: 4 reason: Process /usr/bin/python was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1289399037 uid: 500
Created attachment 459456 [details] File: backtrace
Does exaile actually stop working when this crash report was produced? If so, can you please explain what you were doing when this crash occur? Thanks.
Package exaile-0.3.2.1-1.fc14: * should fix your issue, * was pushed to the Fedora 14 updates-testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing exaile-0.3.2.1-1.fc14' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/exaile-0.3.2.1-1.fc14 then log in and leave karma (feedback).
exaile-0.3.2.1-1.fc14 has been pushed to the Fedora 14 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: https://admin.fedoraproject.org/updates/exaile-0.3.2.1-1.fc14
exaile-0.3.2.1-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.