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 546136 - Internal GStreamer error: state change failed.
Internal GStreamer error: state change failed.
Status: RESOLVED DUPLICATE of bug 471364
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.x
Other All
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-03 20:47 UTC by Marcel
Modified: 2009-04-16 00:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Marcel 2008-08-03 20:47:46 UTC
Please describe the problem:
Playing an audio file in gnome-sound-recorder produces an error and no audio is played.

Steps to reproduce:
1. Open an audio file in gnome-sound-recorder
2. Press play
3. 


Actual results:
Error box popup

Expected results:
Hear an audio file

Does this happen every time?
Yes

Other information:
ERROR: Internal GStreamer error: state change failed.  Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.
DEBUG MESSAGE: gstswitchsink.c(176): gst_switch_commit_new_kid (): /playbin/abin/sink:
Failed to set state on new child.
Comment 1 André Klapper 2008-08-03 21:14:30 UTC
What kind of audio file? which version of gnome-sound-recorder and gstreamer is this exactly, which distribution?
Comment 2 Jan Schmidt 2008-08-03 23:05:19 UTC
That error is indicating that it's unable to connect to the audio device. The error itself has been improved in a later release than whatever you have, but the fundamental problem is that your audio device is busy or misconfigured.

Try taking a look in the System->Preferences->Sound dialog.
Comment 3 Marcel 2008-08-03 23:58:54 UTC
@Andre Klapper
I tried .mp3 and .ogg. An ogg file will generate an additional error;

(gnome-sound-recorder:7756): GStreamer-CRITICAL **: 
Trying to dispose element fakesink, but it is not in the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.

The version of gnome-sound-recorder is 2.22.0.
I don't know the exact version of GStreamer for there are many packets installed in Ubuntu 8.10 64bit by the ubuntu-restricted-extras 15.2.

@Jan Schmidt
My audio device is automatically set to HDA Intel (Alsa mixer) and sound playback/capture to Alsa.
Testing these will give errors;

audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink profile=music: Could not open audio device for playback. Device is being used by another application.

audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink profile=chat: Could not open audio device for playback. Device is being used by another application.

gconfaudiosrc ! audioconvert ! audioresample ! gconfaudiosink profile=chat: Could not open audio device for playback. Device is being used by another application.

Only PulseAudio Sound Server will pass the tests and make the gnome-sound-recorder work as expected.
I did't have any problems with the system sounds, Amarok, Totem, VLC, Psi and some games. Only Quake 3 is muted since I upgraded to new hardware and had a fresh install of Ubuntu while keeping my /home dir.

Maybe my /home dir had some configs based on the old hardware and were not flushed! Are there any known issues when migrating a /home dir?
Comment 4 dsteckbeck 2008-08-15 18:26:08 UTC
I get this error in Fedora 9 also when trying to play .wav files. It seems like this is related to the system playing "click" sounds, because if I press Ctrl+p, I'm able to hear sounds. But if I click the play button with the mouse, I hear the system generated "click" and get the error message immediately after.
Comment 5 Tim-Philipp Müller 2009-04-16 00:19:10 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 471364 ***