Created attachment 181479 [details] attachment 136809 [details] in PP2016, LO 7.4b1 and 7.5 nightly attachment 136809 [details] from bug 112851 contains two charts without data, but displaying data table. These charts were displayed in Impress as empty skeletons, very similar to PP. Recently this regressed, now everything is crushed to the left side of the charts. 1, Open attachment 136809 [details] 2, Compare to how it looks in PP Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 5df1bb4b1b222be00d25097660c4ee33542896ea CPU threads: 14; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: threaded bibisected in win-75 to: https://git.libreoffice.org/core/+/6b481f8bb44a14ebbfe010476cf2ca3728e7d539 author Tomaž Vajngerl <tomaz.vajngerl@collabora.co.uk> Mon May 16 16:10:02 2022 +0900 committer Tomaž Vajngerl <quikee@gmail.com> Sun Jul 17 21:49:32 2022 +0200 chart2: add DataTable to AxisProperties, take account at rendering Adding CC to: Tomaž Vajngerl
Reproduced in Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: db4ac0542a33ba2ff4e64717ca1eb6de563f1a8c CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-ZA (es_ES.UTF-8); UI: en-US Calc: threaded
Dear Gabor Kelemen (allotropia), 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
Regression fixed with the following. Since other ticket is similar, bisected to the same regressoin commit, I mark as duplicate, regardless this is earlier. Still not ideal, but seems good enough for this one to be closed. commit 9a1336e81c84c3386658eff25da34eca7fd86b77 [log] author Noel Grandin <noel.grandin@collabora.co.uk> Thu Oct 24 13:31:28 2024 +0200 tdf#153182 PPTX Chart with datamodel rendered incorrectly Partial fix. (*) fixed bugs where the use of continue in loops meant that a tracking variable was not being updated (*) improved exception message in TableModel::getCellByPosition (*) rather than exiting the view generation process with an exception, log a warning and skip that part of the view process The root of the problem here is that we don't seem to be importing data-tables from PPTX properly. I suspect that we need more import code, in particular, we probably need to read some flag that indicates if we have header rows and columns. *** This bug has been marked as a duplicate of bug 153182 ***