Bug 96620 - Chart is lost as soon as custom formatting is involved
Summary: Chart is lost as soon as custom formatting is involved
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
Version:
(earliest affected)
5.0.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Chart
  Show dependency treegraph
 
Reported: 2015-12-20 11:53 UTC by szotsaki
Modified: 2023-03-09 03:26 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Calc sheet with chart example (14.12 KB, application/vnd.oasis.opendocument.spreadsheet)
2015-12-20 11:53 UTC, szotsaki
Details

Note You need to log in before you can comment on or make changes to this bug.
Description szotsaki 2015-12-20 11:53:51 UTC
Created attachment 121432 [details]
Calc sheet with chart example

1.) Have a Calc sheet with some data inside with a chart (attached).
2.) Double click on the chart to get into its edit mode.
3.) Double click on the Y axis numbering.
4.) Change the font family to an other one (I chose DejaVu Sans, but it's up to you).

Now, if you still can see the bars inside the chart, try
- copy-paste the whole chart or
- copy the sheet in Calc or
- just reopen the .ods file.

The bars inside the chart is gone.
Comment 1 Buovjaga 2015-12-26 15:59:57 UTC
Repro with document.

Win 7 Pro 64-bit Version: 5.2.0.0.alpha0+
Build ID: a4764cfa80270f973da5861d0ddc28298bf16f4d
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-12-24_22:45:12
Locale: fi-FI (fi_FI)
Comment 2 QA Administrators 2017-01-03 19:57:33 UTC Comment hidden (obsolete)
Comment 3 szotsaki 2017-01-04 08:13:00 UTC
Reproducible with 5.2.3.3 on openSUSE Leap 42.2.
Comment 4 szotsaki 2018-03-07 18:04:00 UTC
Reproducible with 
Version: 6.0.2.1
Build ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
Locale: hu-HU (hu_HU); Calc: CL
Comment 5 QA Administrators 2019-03-08 03:40:07 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2021-03-08 04:02:32 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2023-03-09 03:26:35 UTC
Dear szotsaki,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug