GNOME Bugzilla – Bug 567953
criticals when opening gnumeric file with guppi graphs
Last modified: 2010-07-31 14:28:24 UTC
Version: r17071 OS: Ubuntu Intrepid Steps to reproduce - Import Attachment 6201 [details] (.gnumeric file) from Bug 66666 Console output: Unexpected element 'gmr:Vectors' in state : Workbook -> Sheets -> Sheet -> Objects -> GnmGraph Unexpected element 'graph:Graph' in state : Workbook -> Sheets -> Sheet -> Objects -> GnmGraph GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Unexpected element 'gmr:Vectors' in state : Workbook -> Sheets -> Sheet -> Objects -> GnmGraph Unexpected element 'graph:Graph' in state : Workbook -> Sheets -> Sheet -> Objects -> GnmGraph GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Unexpected element 'gmr:Vectors' in state : Workbook -> Sheets -> Sheet -> Objects -> GnmGraph Unexpected element 'graph:Graph' in state : Workbook -> Sheets -> Sheet -> Objects -> GnmGraph GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Unexpected element 'gmr:Vectors' in state : Workbook -> Sheets -> Sheet -> Objects -> GnmGraph Unexpected element 'graph:Graph' in state : Workbook -> Sheets -> Sheet -> Objects -> GnmGraph GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Backtrace:
+ Trace 211584
This file contains guppi graphs that we do not import anymore, although GnmGraph is still handled in xml-sax-red.c. I don't know what should be done.
I think we should be able to recognize that they are Guppi graphs and then load the into some corresponding goffice graph.
> I think we should be able to recognize that they are Guppi graphs and then load > the into some corresponding goffice graph. Realistically we can't be talking about a lot of files. It makes more sense to help any victims out there in converting by hand. I think the files would have to be from 1.0.x or something like it.
Actually, it should be possible to import Guppi graphs, at least approximately.
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report. Not sure that the graphs have the same appearance than in 1.0.x though.