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 728176 - Segfault using version 1.12.6, Ubuntu 13.10, works fine with 1.10.17 / Ubuntu 12.04.4
Segfault using version 1.12.6, Ubuntu 13.10, works fine with 1.10.17 / Ubuntu...
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: 2014-04-14 10:45 UTC by Marlon Nelson
Modified: 2014-04-14 12:31 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Simple spreadsheet causes Gnumeric to segfault (19.55 KB, application/x-gnumeric)
2014-04-14 10:45 UTC, Marlon Nelson 		Details

Description Marlon Nelson 2014-04-14 10:45:09 UTC 
Created attachment 274253 [details]
Simple spreadsheet causes Gnumeric to segfault

The attached spreadsheet causes Gnumeric 1.12.6 to segfault, but Gnumeric 1.10.17 opens it fine.

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 13.10
Release:	13.10
Codename:	saucy
$ 
$ gnumeric -v
gnumeric version '1.12.6'
datadir := '/usr/share/gnumeric/1.12.6'
libdir := '/usr/lib/gnumeric/1.12.6'
$ 
$ gnumeric C.gnumeric 
Segmentation fault (core dumped)
$

Here's the info from a different computer that opens it fine:

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 12.04.4 LTS
Release:	12.04
Codename:	precise
$ 
$ gnumeric -v
gnumeric version '1.10.17'
datadir := '/usr/share/gnumeric/1.10.17'
libdir := '/usr/lib/gnumeric/1.10.17'
$
Comment 1 Morten Welinder 2014-04-14 12:31:15 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

See bug 707047 for a workaround.

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