GNOME Bugzilla – Bug 655453
Movies keep on getting some kind of pa_stream failure
Last modified: 2013-07-22 14:07:46 UTC
When playing a file on located on my server (over ssh) I keep getting these errors. I'm unsure if this is a bug in Pulseaudio, GStreamer, gvfs or Totem itself, so trying to file it here first. This is the error dialog that comes up: "An error occurred. Disconnected: Connection terminated" And after that: "An error occured. pa_stream_cork() failed: Connected terminated" Both of the above occurs twice. This is what's outputted in the terminal: No accelerated IMDCT transform found ** Message: Error: pa_stream_writable_size() failed: Connection terminated pulsesink.c(1644): gst_pulseringbuffer_commit (): /GstPlayBin2:play/GstPlaySink:playsink0/GstBin:abin/GstBin:audiosinkbin/GstGConfAudioSink:audio-sink/GstBin:bin2/GstAutoAudioSink:autoaudiosink1/GstPulseSink:autoaudiosink1-actual-sink-pulse ** Message: Error: Disconnected: Connection terminated pulsesink.c(369): gst_pulsering_is_dead (): /GstPlayBin2:play/GstPlaySink:playsink0/GstBin:abin/GstBin:audiosinkbin/GstGConfAudioSink:audio-sink/GstBin:bin2/GstAutoAudioSink:autoaudiosink1/GstPulseSink:autoaudiosink1-actual-sink-pulse ** Message: Error: pa_stream_cork() failed: Connection terminated pulsesink.c(1006): gst_pulsering_set_corked (): /GstPlayBin2:play/GstPlaySink:playsink0/GstBin:abin/GstBin:audiosinkbin/GstGConfAudioSink:audio-sink/GstBin:bin2/GstAutoAudioSink:autoaudiosink1/GstPulseSink:autoaudiosink1-actual-sink-pulse ** Message: Error: Disconnected: Connection terminated pulsesink.c(369): gst_pulsering_is_dead (): /GstPlayBin2:play/GstPlaySink:playsink0/GstBin:abin/GstBin:audiosinkbin/GstGConfAudioSink:audio-sink/GstBin:bin2/GstAutoAudioSink:autoaudiosink1/GstPulseSink:autoaudiosink1-actual-sink-pulse
That means that PulseAudio died.
Can this be closed? Andreas, do you still get this with more recent versions of things (GStreamer 1.x, recent-ish pulseaudio)?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!