Bug 735639 - audacious 2.5.4 does not find decoders
Summary: audacious 2.5.4 does not find decoders
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: audacious
Version: 15
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Michael Schwendt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-04 13:25 UTC by Dirk Foerster
Modified: 2011-09-04 18:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-04 17:26:45 UTC


Attachments (Terms of Use)
Error message screen shot (48.85 KB, image/png)
2011-09-04 17:43 UTC, Dirk Foerster
no flags Details
Another error message this time for a music file and not a stream (41.80 KB, image/png)
2011-09-04 17:49 UTC, Dirk Foerster
no flags Details

Description Dirk Foerster 2011-09-04 13:25:25 UTC
Description of problem:
Installed streamtuner2 which triggered audacious 2.5.4 installation.
audacious 2.5.4 does not find decoders although exaile and rhythmbox, for instance, do play back music.

Version-Release number of selected component (if applicable):
audacious 2.5.4

How reproducible:
Select any music file or stream to be played by audacious 2.5.4 .

Steps to Reproduce:
1.Select any music file or stream to be played by audacious 2.5.4 .
2.
3.
  
Actual results:
No play back. Error message says cannot find decoders.

Expected results:
Playback of music.

Additional info:

Comment 1 Michael Schwendt 2011-09-04 17:26:45 UTC
I cannot take you serious. There are other users running Audacious just fine. You need to give details, not limited to the output of

  rpm -qa audacious\*

Comment 2 Dirk Foerster 2011-09-04 17:40:52 UTC
(In reply to comment #1)
> I cannot take you serious. There are other users running Audacious just fine.
> You need to give details, not limited to the output of
> 
>   rpm -qa audacious\*

#   rpm -qa audacious\*
audacious-2.5.4-1.fc15.x86_64
audacious-libs-2.5.4-1.fc15.x86_64
audacious-plugins-2.5.4-1.fc15.x86_64

Please see also photo of error message which I'll upload.

Comment 3 Dirk Foerster 2011-09-04 17:43:18 UTC
Created attachment 521393 [details]
Error message screen shot

Comment 4 Michael Schwendt 2011-09-04 17:46:56 UTC
With just those packages, you're just missing plugins packages for MP3 and similar
audio formats Fedora cannot provide ( http://fedoraproject.org/wiki/Forbidden_items ). You can still play lots of non-patented formats including Ogg Vorbis, FLAC, WavPack and others.

You can download additional plugin packages for Audacious at the same place where you downloaded plugin packages for GStreamer (which rhythmbox is based on unlike Audacious). For example, there's an audacious-plugins-freeworld package at a well-known add-ons repository. Alternatively, start with "yum list audacious\*" to show all available Audacious packages. Inspect them further with "yum info ..." or use your favourite package installer.

Comment 5 Dirk Foerster 2011-09-04 17:49:34 UTC
Created attachment 521394 [details]
Another error message this time for a music file and not a stream

Comment 6 Dirk Foerster 2011-09-04 17:58:50 UTC
(In reply to comment #4)
> With just those packages, you're just missing plugins packages for MP3 and
> similar
> audio formats Fedora cannot provide (
> http://fedoraproject.org/wiki/Forbidden_items ). You can still play lots of
> non-patented formats including Ogg Vorbis, FLAC, WavPack and others.
> 
> You can download additional plugin packages for Audacious at the same place
> where you downloaded plugin packages for GStreamer (which rhythmbox is based on
> unlike Audacious). For example, there's an audacious-plugins-freeworld package
> at a well-known add-ons repository. Alternatively, start with "yum list
> audacious\*" to show all available Audacious packages. Inspect them further
> with "yum info ..." or use your favourite package installer.

Found that. Now audacious plays back music. Thank you.


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