Bug 88399 - CALC corrupts ODS file after renaming range row in chart
Summary: CALC corrupts ODS file after renaming range row in chart
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.2.8.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-14 12:31 UTC by Carlos Roberto
Modified: 2015-01-14 17:33 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Old Table 1.ods (16.38 KB, application/vnd.oasis.opendocument.spreadsheet)
2015-01-14 12:31 UTC, Carlos Roberto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos Roberto 2015-01-14 12:31:59 UTC
Created attachment 112213 [details]
Old Table 1.ods

How to reproduce:

1- Open attachment Old Table 1.ods
2- Select Chart with double left click.
3- Right click on chart them select Data Ranges...
4- Select Data Series Tab.
5- On Row 9 click in Range for Name and write "anything"
6- Click in OK, deselect Chart and finally save file and exit.
7- Open Old Table 1.ods again and all dates (2009 to 2013) in chart will be messed. Now you have a broken and corrupted file.

This bug also leads to Bug 88388.
Comment 1 Robinson Tryon (qubit) 2015-01-14 12:39:13 UTC
Comment on attachment 112213 [details]
Old Table 1.ods

fix mimetype
Comment 2 raal 2015-01-14 12:54:49 UTC
I can not confirm with LO 4.3.5, win7.
Please test with version 4.3.5, https://www.libreoffice.org/download/libreoffice-fresh/

setting as needinfo, set as unconfirmes after test with LO 4.3.5
Comment 3 Carlos Roberto 2015-01-14 13:16:46 UTC
Hi raal.

I cannot reproduce with LO 4.3.4.1, it will take some time to download LO 4.3.5, so close it as fixed?
Comment 4 Robinson Tryon (qubit) 2015-01-14 17:33:29 UTC
(In reply to morid_rhosard from comment #3)
> Hi raal.
> 
> I cannot reproduce with LO 4.3.4.1, it will take some time to download LO
> 4.3.5, so close it as fixed?

Sure, we'll marks it as RESOLVED WORKSFORME.

If the same problem shows up in a 4.3.4 or 4.3.5 build at some later date, please change the status back to UNCONFIRMED and we'll continue to investigate.