Bug 476436 - audacious don't start
audacious don't start
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: audacious (Show other bugs)
10
i386 Linux
low Severity low
: ---
: ---
Assigned To: Ralf Ertzinger
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-12-14 13:02 EST by Nuno Dias
Modified: 2009-06-03 16:31 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-06-03 16:31:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nuno Dias 2008-12-14 13:02:30 EST
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 15:17:44 EST
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 16:31:13 EDT
> 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".

Note You need to log in before you can comment on or make changes to this bug.