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 734373 - Small spreadsheet file causes gnumeric segmentation fault
Small spreadsheet file causes gnumeric segmentation fault
Status: RESOLVED DUPLICATE of bug 707047
Product: Gnumeric
Classification: Applications
Component: import/export other
unspecified
Other Linux
: Normal major
: ---
Assigned To: Morten Welinder
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2014-08-06 17:29 UTC by rchildre@charter.net
Modified: 2014-08-06 17:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Small gnumeric spreadsheet file causes segmentation fault (3.18 KB, application/x-gnumeric)
2014-08-06 17:29 UTC, rchildre@charter.net 		Details

Description rchildre@charter.net 2014-08-06 17:29:12 UTC 
Created attachment 282725 [details]
Small gnumeric spreadsheet file causes segmentation fault

The attached gnumeric file was auto-saved from Gnumeric 1.12.6 running on x86 64-bit LUBUNTU 13.11.0-26-generic.  The spreadsheet is very simple and small. After an auto-save, Gnumeric crashed on a segmentation fault. There is something wrong with the file, because Gnumeric runs great otherwise. The problem may be associated with a split view on Row 2.  

Overall, Gnumeric is a very impressive product and we much prefer it over Excel.  Based on the robustness and feature rich capabilities of Gnumeric, it is surprising such a simple, small spreadsheet file could cause a segmentation fault and otherwise, unrecoverable issue.  This bug causes one to rethink use of the native gnumeric file extension over XML.  Perhaps you can take a look at the file to discover a root cause?

Thanks!
Comment 1 Morten Welinder 2014-08-06 17:47:36 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.

(Note the workaround in bug 707047.)

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