Bug 37595 - spreadsheet gets corrupted when opening xlsx with "frozen" row
Summary: spreadsheet gets corrupted when opening xlsx with "frozen" row
Status: RESOLVED DUPLICATE of bug 40070
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.3.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-25 10:55 UTC by jgib
Modified: 2012-09-06 10:05 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
weird rows in wrong place (22.35 KB, image/png)
2011-05-25 10:55 UTC, jgib 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jgib 2011-05-25 10:55:37 UTC 
Created attachment 47155 [details]
weird rows in wrong place

Steps to reproduce:
1.  Open ods speadsheet.
2.  "Freeze" a row.
3.  Scroll down a page or two of data
4.  Save as .xlsx format (microsoft)
5.  Re-open spreadsheet.  The row names will now randomly be in the middle of the data.  Row 1 will have both the 1st column data AND the letter names (A, B, C, etc.)

Screenshot attached.

Use case - I open a speadsheet I've created and save to xlsx since MS Office for mac doesn't support ODF.  He opens it - it's all wacked out.
Comment 1 Björn Michaelsen 2011-12-23 12:05:08 UTC 
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 2 Florian Reisinger 2012-08-14 14:03:11 UTC 
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 3 Florian Reisinger 2012-08-14 14:04:06 UTC 
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 4 Florian Reisinger 2012-08-14 14:08:39 UTC 
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 5 Florian Reisinger 2012-08-14 14:10:41 UTC 
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 6 sasha.libreoffice 2012-09-06 10:05:34 UTC 

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