Created attachment 154212 [details]
Example compared in MSO and different LO after save and open round-trip
If we *open* XLSX attachment 102146 [details] from Bug 80816 it's mostly fine, except some format issues, most notably title text format.
MSO opens as PDF attachment 102601 [details].
If we *save* as XLSX in LO, there used to be more differences, as shown in PDF attachment 102604 [details].
But now in LO 6.4+, data in two graphs is completely missing on filesave and that's this bug.
I'd call this a regression.
LO 5.2 used to show data, 5.3 no.
(In reply to Timur from comment #0)
> If we *open* XLSX attachment 102146 [details] from Bug 80816 it's mostly
> fine, except some format issues, most notably title text format.
FYI that is known as bug #78027
Regression introduced by:
author Eike Rathke <email@example.com> 2016-10-27 12:52:01 +0200
committer Eike Rathke <firstname.lastname@example.org> 2016-10-27 12:52:34 +0200
commit 02af87fdd76bc94fb51aeb160c74d6f719c42c63 (patch)
parent 91114f68e0a81d4f2a5354bc6057f62c22c780b4 (diff)
Resolves: tdf#103531 OOXML: write external file ID within quoted sheet names
Bisected with: bibisect-linux-64-5.3
Adding Cc: to Eike Rathke
Still reproducible in
Build ID: 718f540fb63af27c1336f89213444e9af753b8a9
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3;
Locale: en-US (en_US.UTF-8); UI-Language: en-US
@Xisco: The cached external data here is not written to OOXML, hence when reloaded all data in the chart is blank; that mentioned commit is not the culprit, test-reverting the change it still fails.
Could I have an actually matching bisect please?
I have an idea what's missing, but maybe there's an indicator why and why it worked before, if it really did.. unfortunately my earliest local build is 5-3-7 so I can't check, compiling that old code with a new compiler doesn't work without modifications.
It may of course be that things worked differently in the past and the commit somehow made it fail and then afterwards things were changed so that it now doesn't matter and fails anyway, so bisecting correctly misleads.
The same in Excel 97 .xls binary format. The external data is only referenced in the chart data ranges, not in sheet formulas, hence not added to the XclExpSupbookBuffer. I doubt this ever worked, but if so would be interested in the real bisect.
Unassigning for the time being.
I just bisected it and it points me to the same commit ( either using the UI or command line... --convert-to ). I double checked using git checkout HEAD~1. OTOH, the problem with xls files can be reproduced with previous versions
@Buovjaga, @Raal, would it be possible to bisect this issue on windows to see if it points to the same commit ? ( 02af87fdd76bc94fb51aeb160c74d6f719c42c63 in win-5-3 repo )
(In reply to Xisco Faulí from comment #10)
> @Buovjaga, @Raal, would it be possible to bisect this issue on windows to
> see if it points to the same commit ? (
> 02af87fdd76bc94fb51aeb160c74d6f719c42c63 in win-5-3 repo )
Actually I had that repo on win so I bisected it too. Both linux and windows repositories point me to the same commit
Sorry for the basic question, but does bibisect commit has multiple code commits or just that one?
(In reply to Timur from comment #12)
> Sorry for the basic question, but does bibisect commit has multiple code
> commits or just that one?
Just this one.
Also, the backported commit (bug 103531 comment 4) can be found in bibisect-linux-64-5.2, and is the cause of the same regression in that repo.
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!