Bug 651821 - [abrt] exaile-0.3.2.0-2.fc14: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] exaile-0.3.2.0-2.fc14: Process /usr/bin/python was killed by signal 11...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: exaile
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Deji Akingunola
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:12b34c4eb798cb035ead7700b09...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-10 11:40 UTC by Kris Buytaert
Modified: 2011-01-07 20:35 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-01-07 20:35:18 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (95.40 KB, text/plain)
2010-11-10 11:40 UTC, Kris Buytaert 		no flags Details
View All

Description Kris Buytaert 2010-11-10 11:40:40 UTC 
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
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 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289389136
uid: 500

How to reproduce
-----
I think this crash happened at the end of exaile playing a song.
Comment 1 Kris Buytaert 2010-11-10 11:40:42 UTC 
Created attachment 459405 [details]
File: backtrace
Comment 2 Armin 2010-11-23 21:12:17 UTC 
Package: exaile-0.3.2.0-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Started exaile
2. searched for deepmix.ru from "Radio Stations"
3. clicked on it
4. BAM!
Comment 3 Kris Buytaert 2011-01-07 20:35:18 UTC 
As mentioned in  https://bugzilla.redhat.com/show_bug.cgi?id=657971#c17
this is most probably a bug in ffmpeg which is provided by rpmfusion. and which
is solved by installing gstreamer-plugins-ugly
Note You need to log in before you can comment on or make changes to this bug.