GNOME Bugzilla – Bug 547310
Sound Recorder crashes with GStreamer state-change error
Last modified: 2008-09-09 20:18:01 UTC
Using gnome-sound-recorder 2.22.0: I press Record (I speak a bit).then Stop, then Play and I get this pop-up: Internal GStreamer error: state change failed. Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer. Here is my uname -a Linux melodic 2.6.25.11-97.fc9.i686 #1 SMP Mon Jul 21 01:31:09 EDT 2008 i686 i686 i386 GNU/Linux ========== Here is what I got from bug buddy ==================== Failed to set state on new child. ** (gnome-sound-recorder:7709): WARNING **: Unknown codec ID 86022, please add here 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. (gnome-sound-recorder:7709): 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. =================================================================== To be fair, my sound system is flaky. Usually, the Sound Recorder works for me, but several times it has not. Skype does not work, with messages of "Failed Call" or "Error in Playback" (although, Skype did work a couple of months ago). I only recently got my PulseAudio server running by putting myself into the pulse-rt group. I understand that my HDA Intel audio system is not well-supported?
I have the same problem. Found it when I tried to install Skype.
This sounds like a configuration issue (possibly skype hogs the audio device; in any case, the underlying bug is in gconfaudiosink and is that we don't show the proper error message from alsasink; most likely it's "Device in use" though; this should be fixed in newer versions of gst-plugins-good; hda intel should generally be supported ok-ish as far as I know). *** This bug has been marked as a duplicate of 471364 ***