[gstreamer-bugs] [Bug 337596] 'Generic error' when destination is a remote system

Wed Apr 12 04:59:59 PDT 2006

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=337596
 GStreamer | gst-plugins-base | Ver: 0.10.5

Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |critical
           Priority|Normal                      |High

------- Comment #4 from Tim-Philipp Müller  2006-04-12 11:59 UTC -------
What I meant is:

if you do this with GST_DEBUG=*:2 set, you get something like two marked lines
in addition to the normal output whenever GStreamer throws an error:

tim at sceptic:~ $ GST_DEBUG=*:2 gst-launch-0.10 audiotestsrc num-buffers=10 !
gnomevfssink location=sftp://192.168.0.1/foo.txt
Setting pipeline to PAUSED ...

====> WARN  (0x80509c8 - 0:00:00.313704000)         gnomevfssink( 2459)
gstgnomevfssink.c(388):gst_gnome_vfs_sink_open_file:<gnomevfssink0> error:
Could not open vfs file "sftp://192.168.0.1/foo.txt" for writing: Access
denied.
====> WARN  (0x80509c8 - 0:00:00.314133000)         gnomevfssink( 2459)
gstgnomevfssink.c(388):gst_gnome_vfs_sink_open_file:<gnomevfssink0> error:
system error: Resource temporarily unavailable

ERROR: Pipeline doesn't want to pause.
ERROR: from element /pipeline0/gnomevfssink0: Could not open vfs file
"sftp://192.168.0.1/foo.txt" for writing: Access denied.
Additional debug info:
gstgnomevfssink.c(388): gst_gnome_vfs_sink_open_file ():
/pipeline0/gnomevfssink0:
system error: Resource temporarily unavailable
Setting pipeline to NULL ...
FREEING pipeline ...

So if you do the same with sound-juicer and you do not get those two extra
lines, that indicates that it is not GStreamer throwing the error.
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If
you have time and can still reproduce the bug, please read
http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to
reproduce this bug.

You'll also need to add a stack trace; please see
http://live.gnome.org/GettingTraces for more information about how to do so.

-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.