Created attachment 54511 [details] This the presentation file that demonstrates the problem A chart created with Presentation has large grey blocks in the upper left portion of the display. They persist until the user clicks "reset all data points". I am attaching the presentation file and a before and after "reset all data points" screenshot. I've circled the blocks with green in the "before" screenshot. I have searched for what "reset all data points" does and cannot find any mention of it. It's nice that "reset all data points" fixes it however it's seems unnecessary to display the grey blocks whether the data points are fixed or not.
Created attachment 54512 [details] This shows the unwanted grey blocks
Created attachment 54513 [details] This shows the screen after "reset all data points" has been clicked
Thanks for bugreport reproduced in 3.3.4 and 3.5.1 on Fedora 64 bit and in 3.4.3 on Windows XP 32 bit Inside of presentation Chart saved in the directory "ObjectReplacements" as an binary file which contains "VCLMTF". The binary file containing the VCLMTF string is a StarView Meta file. If I extract this file and open by LibreOffice, it looks like on first screenshot. Therefore this file contains problem. IMHO after "reset all data points" this file re-generated with no error. msOffice 2007 opens attached odp file without problem. IMHO it not uses this strange file and therefore opens correctly. @ jkonecny@rmtohio.com Sorry, I can not find "reset all data points". Where I can find it? And how created this presentation? If problem appears with newly created presentation, please, provide step-by-step instructions how to reproduce this problem.
To access "Reset all data points" you need to double click the Chart to get into edit mode. Then right click on the data series represented by the line "Wood" and then you will see "Reset all data points" in the pop-up menu. "Reset all data points" appears in the right click menu until you click it and then it disappears. I'm really not sure what it does but it fixes it. This presentation file was originally created by an unknown version of OpenOffice. It has been used with various versions of OpenOffice and now with various versions of LibreOffice. I have no idea on how to make it happen from a fresh chart. Data was added to this chart over a period of time and various format changes were made I am sure. Sorry I cannot give the steps to recreate the problem. It did not appear for quite some time after the creation.
Thanks for explanations. I found this reset. Nothing happens in my case. IMHO problem is inside of presentation, not in Impress. We need somebody with better knowledge of Impress than me. Currently, if You have only one presentation with this problem, it is more simply to re-create it from scratch. If exist many such presentations, we need some trick to fix them. For example save to another format and reload or open by another program and save again. I dislike these variants, but can not invent something better.
Created attachment 59273 [details] resaved by msPP 2007, as example of bad but quick workaround
IMHO saving into FODT format by Impress and reloading works well.
I mean FODP format
Created attachment 59274 [details] screen shot of from attachment 59273 [details] when opened with 3.5.2.2 I loaded attachment 59273 [details] and the results look poor under 3.5.2.2.
Thanks for screenshot. It is regression of 3.5 version of LibreOffice In 3.3.4 and 3.4.3 it opens correctly Sorry for such situation. And how about saving into Flat ODP?
FODP seems to solve the problem.
Confirmed with: LO 3.5.5.3 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit Reset all data points fixes the presentation. Saving as fodp also. Another thing is that when I open this presentation a rectangular box under Yr/Yr is presented. It is missing from the screenshots.
We've switched to msoffice. Feel free to close this.
Even worse now on OSX 10.10 with master 440 alpha, see attached screenshot
Created attachment 108172 [details] bad chart display in Impress
** 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.0.4 or later) 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 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
Confirming also in ersion: 5.2.0.0.alpha0+ Build ID: ce3d3f5543e3e132a3473af27aa2c827336add0f CPU Threads: 2; OS Version: -; UI Render: default; Locale : fr-FR (fr.UTF-8) it really does look bad, not surprising the original poster switched to MSO
** 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.1.6 or 5.2.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-20170103
Dear jkonecny, 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
Dear jkonecny, 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