Bug 476436

Summary: audacious don't start
Product: [Fedora] Fedora Reporter: Nuno Dias <nuno.dias>
Component: audaciousAssignee: Ralf Ertzinger <redhat-bugzilla>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 10CC: bugs.michael, redhat-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-06-03 20:31:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nuno Dias 2008-12-14 18:02:30 UTC
Description of problem:
Audacious do not start

Version-Release number of selected component (if applicable):
audacious-plugins-1.5.1-2.fc10.i386
audacious-libs-1.5.1-4.fc10.i386
audacious-1.5.1-4.fc10.i386

How reproducible:

Steps to Reproduce:
1. Start audacious
2.
3.
  
Actual results:
Audacious do not start

Expected results:
audacious start

Additional info:
I tried to use gdb to get more information ...
I/O warning : failed to load external entity "/home/ndias/.config/audacious/playlist.xspf"
[New Thread 0xb5a2bb90 (LWP 11720)]

Program received signal SIGILL, Illegal instruction.
0x080a3104 in ui_skinned_equalizer_slider_set_position (widget=0x82ee6f0, 
    pos=0) at ui_skinned_equalizer_slider.c:355
355	    priv->position = 25 - (gint) ((pos * 25.0) / EQUALIZER_MAX_GAIN);
Missing separate debuginfos, use: debuginfo-install libtdb-1.1.1-23.fc10.i386

But I can't get debuginfo package to libtdb

Comment 1 Nuno Dias 2008-12-14 20:17:44 UTC
I update to audacious-1.5.1-5.fc10.i386 from the update-testing repo, and the audacious now starts.

The only problem is the skins, I can't load any new skin, the only skins that are available is the defaults from the package.

Comment 2 Michael Schwendt 2009-06-03 20:31:13 UTC
> The only problem is the skins, I can't load any new skin,
> the only skins that are available is the defaults from the package.  

That would be a different problem that in the original report. Consider opening a separate ticket with detailed steps on how to reproduce it. In particular, describe what you mean with "I can't load any new skin".