Created attachment 121237 [details] Example Calc file in .ods format Description: After saving a Calc document in .xlsx format, closing, and then reopening it, the error bar line style is set to none, resulting in the error bars no longer being drawn. (They can still be accessed via the "Select Chart Element" drop down, however.) Steps to reproduce: 1. Create a document with (y) error bars or open a .ods document with them. 2. Select "Save As" from the File menu, and save the file in .xlsx format. 3. Close the document. 4. Reopen the document in Calc. 5. The error bars are invisible! Expected behavior: Error bars would be visible. Current behavior: Error bars are not visible. PS. I've attached an example file in .ods format which can be saved in .xlsx format, as well as an .xlsx version of the same document that already has been converted. As an extra added bonus, the converted file also does not show its Data Series chart columns for the same reason (i.e. their line style has been set to none). PPS. I know there was a Mac OS bug (Bug 62312) with very similar symptoms that was ostensibly fixed, but here it is again (?) in Linux. I'm running version 5.0.3.2. I have no idea what the earliest release the bug appears in, but I'm pretty sure it also occurred under 4.3.x, which I was running before installing 5.0.
Created attachment 121238 [details] Example Calc document saved in .xlsx format
Note that this is not an effect of the width of the error bar being set to the default value of "0.00" (which is also displayed in the error bar dialog box - before and after saving in .xlsx format).
Hi @Marisano, reproducible. Win10x64 With 4.1.6 / 4.2.8.2 / 4.3.7.2 / 4.4.7.2 also the bars are lost. With Version: 5.0.4.1 (x64) Build ID: 2def61bcbb29a7a8611b833682fe1291910b11ad, onl
Hi, Reproducible on Manjaro Linux, x86-64. Version 5.1.1.3 (but the bug has been present for a long time).
*** Bug 99203 has been marked as a duplicate of this bug. ***
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
Still. Version: 5.3.3.2 (x64) Build ID: 3d9a8b4b4e538a85e0782bd6c2d430bafe583448 CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; Layout Engine: new; Locale: es-ES (es_ES); Calc: group
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present in 6.0.4.2.
Created attachment 149370 [details] Screenshot of the exported file to .xlsx by LO Master Probably this patch could help here: Balazs Varga committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/b89f239aa9d3d4660380bbd0c893aecde0986032%5E%21 tdf#97575 Chart OOXML: Export ShapeProps of Error Bars It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Created attachment 149371 [details] Exported original file to .xlsx