Steps to reproduce (tested with version 6.3.4.2.0 on Gentoo linux, I wanted to test on latest but that will have to wait until I update libreoffice): 0. Create an empty spreadsheet in LibreOffice calc 1. Create 2 sheets named Sheet1 and Sheet2 in this spreadsheet 2. In Sheet1, set some value at cell A1 3. In Sheet2, write the formula =$Sheet1.A1 in any cell 4. Select cells A1-A2 (or any range of cells containing A1) 5. Drag and drop that selected cells to move them somewhere else. Reference in Sheet2 changes to new location of the content of A1 6. Undo (ctrl+c or edit->undo). Cell in Sheet1 is moved back to A1. Reference in Sheet2 is not changed back to the original. This may "corrupt" a spreadsheet beyond practical recovery if noticed too late.
Repro with Version: 7.0.0.0.alpha0+ (x64) Build ID: b29fb89d0a49fde0f5757774d64a7aba8298ac75 CPU threads: 12; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win; Locale: ru-RU (ru_RU); UI-Language: en-US Calc: CL No repro with Version: 4.4.0.1 Build ID: 1ba9640ddd424f1f535c75bf2b86703770b8cf6f Locale: ru_RU
Regression after https://git.libreoffice.org/core/+/9079da7f62febaf4cef0b77320c31b4e8bb6b5a5
Dear barteks2x, 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
Still present in: Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: CL I was about to report this as a new bug but found it was already reported. I've been getting sporadic corruption for ages and couldn't work out why until I hit on the reason today. There are probably thousands upon thousands of spreadsheets out there that people haven't realised are corrupt because off-sheet references are looking at the wrong cells. Some may disagree, but I'd rate this as very high priority precisely because in a large, complex sheet you might not realise things have gone badly wrong until it's too late.