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 705100 - Corrupt .gnumeric output
Corrupt .gnumeric output
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: import/export other
git master
Other Linux
: High critical
: ---
Assigned To: Morten Welinder
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2013-07-29 19:37 UTC by jutaky
Modified: 2015-05-12 15:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Fixes the issue (459 bytes, patch)
2013-07-30 08:58 UTC, Jean Bréfort
committed Details | Review

Description jutaky 2013-07-29 19:37:35 UTC
Corrupt .gnumeric output.

Git versions of glib, goffice, gnumeric, libgsf and libxml2.

Test case: http://yritystulkki.fi/files/yt22_1_alkavan_tulossuunnitelma_vasek.xls

1) Open with Gnumeric
2) "Save as" into a .gnumeric file
3) Open the .gnumeric file 
4) Observe an error of malformed XML file

--
Juha Kylmänen
Research Assistant, OUSPG
Comment 1 Jean Bréfort 2013-07-30 06:51:47 UTC
It's not corrupt. Just the node is too large to be read by libxml. This is quite annoying.
Comment 2 Jean Bréfort 2013-07-30 08:58:28 UTC
Created attachment 250437 [details] [review]
Fixes the issue
Comment 3 Morten Welinder 2013-07-30 13:23:38 UTC
Interesting, but see
https://bitbucket.org/shlomif/perl-xml-libxml/pull-request/19

Do we lose anything?
Comment 4 Jean Bréfort 2013-07-30 14:00:52 UTC
We need either to enable the huge mode or to save large pixbufs as several blocks, with no one exceeding 2^20 (hoping the limit will never shrink in libxml). Otherwise, just put a photo inside a gnumeric file, and you will not be able to load it back.
What could we loose?
Comment 5 Jean Bréfort 2013-07-30 14:21:18 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.
Comment 6 Morten Welinder 2015-05-12 15:36:00 UTC
See bug 749238 for related fallout.