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 625974 - ZlibCompressor/ZlibDecompressor don't work
ZlibCompressor/ZlibDecompressor don't work
Status: RESOLVED DUPLICATE of bug 619945
Product: vala
Classification: Core
Component: general
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: Vala maintainers
Vala maintainers
Depends on:
Blocks:
 
 
Reported: 2010-08-03 20:14 UTC by Michael Kanis
Modified: 2010-08-20 18:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Kanis 2010-08-03 20:14:42 UTC
I basically adopted the code from http://live.gnome.org/Vala/GIOCompressionSample
Here is my code: http://pastebin.org/446296

The output file should match the input file, but doesn't. It is much smaller. Running the program gives:

(process:17180): GLib-GIO-CRITICAL **: g_converter_convert: assertion `outbuf_size > 0' failed
(process:17180): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(process:17180): GLib-GIO-CRITICAL **: g_converter_convert: assertion `outbuf_size > 0' failed
(process:17180): GLib-CRITICAL **: g_error_free: assertion `error != NULL' failed
(process:17180): GLib-GIO-CRITICAL **: g_converter_convert: assertion `outbuf_size > 0' failed
(process:17180): GLib-CRITICAL **: g_error_free: assertion `error != NULL' failed


I tested with valac 0.8.1 and 0.9.4.
Comment 1 Evan Nemerson 2010-08-04 07:22:42 UTC
I can't reproduce this with latest master or 0.9.4... the pastebin.org code works fine for me. Can someone else give it a try?

Maybe a buggy gio-2.0? I'm running 2.25.11.
Comment 2 Jürg Billeter 2010-08-20 18:51:50 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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