Checked this with 5.4.8 (last daily build), 6.0.3 (Ubuntu 18.04 repo) and 6.1 Alpha1 daily build, the problem manifests in all three versions.
The error was reported by a user on the IRC QA channel, the user did not want to register with bugzilla. The version used by the reporter was LibO 5.4.6
Steps to Reproduce:
1. Download and open attached .fods fils
2. note that there are comments attached to two cells.
3. add some data into a few cells
4. Save the file under a new name with File Save As.
5. Close the file.
6. Open the file you saved with the new name.
Some or all of the comments are missing.
The comments are retained
User Profile Reset: No
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/66.0.3359.139 Chrome/66.0.3359.139 Safari/537.36
Created attachment 142163 [details]
test .fods file
Test Calc file in flat mxl format.
Repro Win LO 6.0.4 and 6.1+ if attached file just saved as, without looking at comments.
But, if comments hovered on and read, saved OK and no repro.
Looks like a regression from 4.2, 4.1 was fine.
Bibisected on Linux with 42max. Unfortunately, there were some builds that refused to start/open the file. The range is: https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=eb24baec8cc465218ca34302c2ddd2a24e023414...2d09baa7802e5d5bf30bd4baafe690f06a1275ec
I think this is probably the cause: https://cgit.freedesktop.org/libreoffice/core/commit/?id=5b483ed15d70bdc34b9520632ee569db0e6c4f9d
Cell note deletion should happen even when no cells exist in the column.
This fixes one of the API test breakages.
Kohei is not dealing with regressions, so I won't add him to CC.
Dear Drew Jensen,
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!