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 318673 - gnomevfssink doesn't propagate "not all bytes were written error" to application level
gnomevfssink doesn't propagate "not all bytes were written error" to applica...
Status: RESOLVED DUPLICATE of bug 309117
Product: GStreamer
Classification: Platform
Component: gst-plugins
0.8.x
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-10-12 14:23 UTC by Frederic Crozat
Modified: 2005-10-12 14:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Frederic Crozat 2005-10-12 14:23:43 UTC 
Version details: 0.8.11
Distribution/Version: Mandriva cooker

-run sound-juicer 2.12.x on an harddisk with no space left
-gnomevfssink will warn on stdout about "Warning: xxxx bytes should be written,
only 0 bytes written" but SJ has no way to get this error.
Comment 1 Tim-Philipp Müller 2005-10-12 14:53:54 UTC 
Marking this a duplicate. Once we know how to best implement this, it should be
implemented the same way for filesink and gnomevfssink anyway.

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