Bug 46120 - 3D Pie chart segmentation disappears after closing and opening a spreadsheet
Summary: 3D Pie chart segmentation disappears after closing and opening a spreadsheet
Status: RESOLVED DUPLICATE of bug 40320
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
(earliest affected)
3.4.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2012-02-15 09:44 UTC by Kay Tate
Modified: 2013-11-28 22:17 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

A minimal testcase (7.50 KB, application/vnd.ms-excel)
2012-03-06 07:24 UTC, Arseny Solokha

Note You need to log in before you can comment on or make changes to this bug.
Description Kay Tate 2012-02-15 09:44:29 UTC
I create a 3D pie chart and put specific colors on the different segments. I save and close the spreadsheet. When I open it again, the pie chart is all one color, no individual segments shown at all. I can hit "reset all data points" to reconstruct the segments, but then I have to change all of them again to the desired colors.
Comment 1 Markus Mohrhard 2012-03-05 15:12:30 UTC
Can you please attach a test document and a detailed instruction how to reproduce it.
Comment 2 Arseny Solokha 2012-03-06 07:24:44 UTC
Created attachment 58060 [details]
A minimal testcase

Reproducible w/ LibreOffice 3.4.5 under GNU/Linux on x86_64 when saving file in "Microsoft Excel 97/2000/XP/2003 (.xls)" format.

Steps to reproduce:
1. Create empty spreadsheet and fill it w/ sample data. For example, putting 1 into A1 and 2 into A2 would be sufficient.
2. Create a pie chart (doesn't really matter, 2D or 3D, normal, exploded or donut).
3. Save the file using the aforementioned filter.
4. Load the file into LibreOffice again. Color of all segments is now set to the first one from the "Charts" palette (blue "Data Series 1" if has not been modified by user).
Comment 3 Kohei Yoshida 2012-03-07 19:58:47 UTC
I'm pretty sure this is a duplicate of Bug 40320, which has been fixed in 3.5.2.

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