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 553861 - zip criticals
zip criticals
Status: RESOLVED FIXED
Product: libgsf
Classification: Core
Component: ZIP
unspecified
Other All
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2008-09-25 22:57 UTC by sum1
Modified: 2008-09-28 18:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
fff7e266f7c26462dbd45cc1fdcd9e0c.zip (1.06 KB, application/zip)
2008-09-25 22:58 UTC, sum1
Details

Description sum1 2008-09-25 22:57:46 UTC
Version: r1007
OS: Ubuntu Hardy

The upcoming, malformed zip file (fff7e266f7c26462dbd45cc1fdcd9e0c.zip) is from
the PROTOS Genome Test Suite:
http://www.ee.oulu.fi/research/ouspg/protos/testing/c10/archive/


Steps to reproduce:
- 'gsf list upcoming_file.zip'


Backtrace (at first critical):

  • #0 IA__g_log
    at /build/buildd/glib2.0-2.16.4/glib/gmessages.c line 516
  • #1 IA__g_return_if_fail_warning
  • #2 gsf_input_name
    at gsf-input.c line 176
  • #3 ls_R
    at gsf.c line 117
  • #4 ls_R
    at gsf.c line 146
  • #5 gsf_list
    at gsf.c line 174
  • #6 main
    at gsf.c line 391


Console output:

** (/home/s/local/bin/gsf:10141): WARNING **: Unable to get child[1] for infile '?' because : Error incorrect zip header @ 108

** (/home/s/local/bin/gsf:10141): CRITICAL **: gsf_input_name: assertion `GSF_IS_INPUT (input)' failed

** (/home/s/local/bin/gsf:10141): CRITICAL **: gsf_input_size: assertion `input != NULL' failed

(/home/s/local/bin/gsf:10141): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Comment 1 sum1 2008-09-25 22:58:38 UTC
Created attachment 119393 [details]
fff7e266f7c26462dbd45cc1fdcd9e0c.zip
Comment 2 Morten Welinder 2008-09-28 18:21:46 UTC
That was a gsf (the tool) problem, not a library problem.

This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.