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 707181 - Gnumeric 1.12.6 crashes in some circumstances when using freeze panes
Gnumeric 1.12.6 crashes in some circumstances when using freeze panes
Status: VERIFIED FIXED
Product: Gnumeric
Classification: Applications
Component: General
1.12.x
Other Linux
: Normal major
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2013-08-31 15:00 UTC by spam.ju
Modified: 2013-08-31 19:37 UTC
See Also:
GNOME target: ---
GNOME version: 3.9/3.10

Attachments
A file with split panes which makes gnumeric crash at opening (1.79 KB, application/octet-stream)
2013-08-31 15:01 UTC, spam.ju 		Details

Description spam.ju 2013-08-31 15:00:16 UTC 
I get a segfault when opening some gnumeric files which use freeze panes.

I reproduced it with a minimal file included. It looks like it happens :
- when opening such a file !
- when the upper part of the botom pane is not visible at first and when you scroll up to make it visible.

Removing the following part of the files let me open the old files again :
<       <gnm:SheetLayout TopLeft="A28">
<         <gnm:FreezePanes FrozenTopLeft="A1" UnfrozenTopLeft="A2"/>
<       </gnm:SheetLayout>

For what it matters i am running mageia cauldron on x86_64 and x86 and i think the issue may be present starting from 1.12.5

Thanks
Comment 1 spam.ju 2013-08-31 15:01:33 UTC 
Created attachment 253690 [details]
A file with split panes which makes gnumeric crash at opening
Comment 2 Andreas J. Guelzow 2013-08-31 17:12:34 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.

*** This bug has been marked as a duplicate of bug 707047 ***
Comment 3 spam.ju 2013-08-31 19:37:47 UTC 
I didn't find the first report.
Anyway, it's great that it is solved. Thanks.