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 712347 - Gnumeric closes down when I attempt to open an old file
Gnumeric closes down when I attempt to open an old file
Status: RESOLVED DUPLICATE of bug 707047
Product: Gnumeric
Classification: Applications
Component: General
1.12.x
Other Linux
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2013-11-15 04:27 UTC by john
Modified: 2013-11-15 13:55 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Multi-sheet file used to record and analyse data from a domestic photovoltaic system. (56.84 KB, application/x-gnumeric)
2013-11-15 04:27 UTC, john 		Details

Description john 2013-11-15 04:27:36 UTC 
Created attachment 259850 [details]
Multi-sheet file used to record and analyse data from a domestic photovoltaic system.

I have recently upgraded from Ubuntu 13.4 to Ubuntu 13.10.

When I tried to open a file I've used previously (solar_PV_arrays_3.gnumeric attached) gnumeric closed down. The same happened when I tied to open an existing Excel file.

I removed and re-installed gnumeric. Same problem.

Next I created a new short spreadsheet, and saved it as test.gnumeric. This opens OK.
Comment 1 Andreas J. Guelzow 2013-11-15 05:33:21 UTC 
This sounds like a known problem with an older version of Gnumeric (1.12.6) that had problems opening files with split panes. Please update to a newer version of Gnumeric.
Comment 2 Morten Welinder 2013-11-15 13:55:47 UTC 
The problem is very likely the frozen pane.  If you need access to your
data right away, this hack removes frozen panes:

gunzip < ~/Download/solar_PV_arrays_3.gnumeric | perl -ne 'if (m{<gnm:SheetLayout TopLeft=".*">} .. m{</gnm:SheetLayout>}) { next; } print;' >~/sss.xml

Other than that, the only fix is to upgrade.

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