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 337596 - 'Generic error' when destination is a remote system
'Generic error' when destination is a remote system
Status: RESOLVED FIXED
Product: sound-juicer
Classification: Applications
Component: general
2.14.x
Other Linux
: Normal normal
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-04-07 08:44 UTC by Sebastien Bacher
Modified: 2006-06-18 16:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastien Bacher 2006-04-07 08:44:56 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/sound-juicer/+bug/38556

"Under Edit -> Preferences -> Music Folder if I select 'Other' from the drop down box I am able to view remote folders accessed via gnome-vfs, eg sftp folders. But if I select one of these folders and press "Extract" (with a known good CD inserted for extraction), I get this error:

Sound Juicer could not extract this CD.
Reason: Generic error"
Comment 1 Sebastien Bacher 2006-04-07 10:29:38 UTC
From the distro bug

"Can you run a test in a terminal:

gst-launch-0.10 audiotestsrc num-buffers=10 ! gnomevfssink location=[some url]

Use the same url you used in SJ but add a filename, i.e. location=sftp://remote.server/home/foo/test"
...
ERROR: from element /pipeline0/gnomevfssink0: Could not open vfs file "sftp..." for writing: Generic error

Reassigning to gstreamer
Comment 2 Tim-Philipp Müller 2006-04-11 17:58:59 UTC
I don't think that error comes from GStreamer or gnomevfssink.

At least in CVS all gnomevfssink errors have proper translated error messages that look like _("could not bla bla bla: %s"), get_gnomevfs_error_string()), so you should definitively have the first bit before the 'Generic Error' in the dialog if this comes from GStreamer.

To make sure you could run sound-juicer from the command line like this:

 $ export GST_DEBUG=*:2
 $ sound-juicer

and then see what it prints there.
Comment 3 Sebastien Bacher 2006-04-12 09:40:56 UTC
Nothing printed from sound-juicer

"gst-launch-0.10 audiotestsrc num-buffers=10 ! gnomevfssink location=sftp"..." prints that:
"...
ERROR: from element /pipeline0/gnomevfssink0: Could not open vfs file "sftp..." for writing: Generic error.
Additional debug info:
gstgnomevfssink.c(383): gst_gnome_vfs_sink_open_file (): /pipeline0/gnomevfssink0:
system error: Resource temporarily unavailable
..."

where the sftp URI has "user:password" replaced by "user"
Comment 4 Tim-Philipp Müller 2006-04-12 11:59:58 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@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.
Comment 5 Tim-Philipp Müller 2006-04-12 12:01:46 UTC
sorry about those standard replies at the end, didn't notice they had been added. Must have mis-clicked somewhere.
Comment 6 Sebastien Bacher 2006-04-17 13:09:56 UTC
reassigning to s-j according to previous comment
Comment 7 Ross Burton 2006-06-18 16:31:55 UTC
The problem must have been fixed as I cannot replicate this any more with Dapper's  Sound Juicer.