After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 513022 - Internal GStreamer error: state change failed.
Internal GStreamer error: state change failed.
Status: RESOLVED DUPLICATE of bug 471364
Product: GStreamer
Classification: Platform
Component: dont know
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-30 07:17 UTC by Parag
Modified: 2008-01-30 19:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Parag 2008-01-30 07:17:31 UTC 
Hi, I am new to Linux, When I tried to play song from Rhythmbox 0.11.3, got the error: Internal GStreamer error: state change failed. and asked me to fill in the details here.

Just as a background, my system froze while playing a song sometime back and I had to re-start Linux. Even though Rhythmbox window was closed. I could see it in the list of processes as "Uninterruptible". I was using Fedora 8. I also have Ubuntu 5.0 and Suse 10.1 installed.

I could not find which version of GStreamer. Sry abt that! if someone can guide me on how to do that. I'll be happy to do so. The gstreamer-properties Test failed with errors like Connection Refused / Resource Busy errors.

Thats all I have at the moment!! Regards.
Comment 1 Tim-Philipp Müller 2008-01-30 14:13:04 UTC 
It's a bad error message you should never have gotten to see. Sorry about that. 

The real problem is probably a configuration/settings error. Go to System => Preferences => Audio and try different settings (on recent gnome/distro versions please, not ancient ubuntu 5.x etc). Probably the chosen device is either busy/used by another application, or doesn't exist, or the sound server (esd/pulseaudio) isn't running.


*** This bug has been marked as a duplicate of 471364 ***
Comment 2 Parag 2008-01-30 19:22:09 UTC 
Thanks Tim,

When i started my system to try and check on this, i found the sound to be working. Could it be that something that was not working (or active) is now active??

I'll try out your steps if I get stuck again and I'm sorry about logging a duplicate bug report, will be more careful (and search b4 logging) next time...

Regards, Parag