From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7 Description of problem: Whenever I try to play a song in rhythmbox, I get the following errors: Internal GStreamer error: negotiation problem. File a bug. Internal GStreamer error: pad problem. File a bug. Could not start pipeline playing Version-Release number of selected component (if applicable): rhythmbox-0.8.8-2 How reproducible: Always Steps to Reproduce: 1.double-click on song or click play with a song selected in the playlist 2. 3. Actual Results: Those errors listed above appears Expected Results: a song should have played Additional info: went through a few steps with the team at Gnome and here's what we found: -gstreamer is the RH version of gstreamer; from the Freshrpms repository I have also added gstreamer-plugins-extra-audio, extra-video, and tools-dvd; -oggs can play in ogg123, xine, mplayer, xmms, and amaroK -running st-launch-ext-0.8 01_Anberlin_Blueprints_For_The_Black_Market_Readyfuels.ogg No configuration file /home/emesa/.gst found. You might want to create one. This is not an error, just a friendly reminder... Check the man page. Running command-line gst-launch-0.8 filesrc location="01_Anberlin_Blueprints_For_The_Black_Market_Readyfuels.ogg" ! oggdemux ! vorbisdec ! audioconvert ! osssink RUNNING pipeline ... makes the song play - so gstreamer works -I CAN listen to streaming media in rhythmbox -finally, there is ONE mp3 that plays. I tried playing other mp3s, but they don't work. I tried other mp3s from the same folder - no dice. I tried using the file command to see if there was a difference, but no - there wasn't. -I have a lot of other programs that depend on the other gstreamer plugins, so I'd like to fix this w/o disturbing those, if possible.
Thank you for the bug report. However, Fedora Project no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem against Fedora Legacy component