Description: Copied column/row labels reference wrong cell until file is reloaded. Steps to Reproduce: 1. Make a new spreadsheet 2. enable Tools -> Options... -> LibreOffice Calc -> Calculate -> Automatically find column and row labels 3. Enter these data into the first sheet: A1: a A2: 1 A3: 2 A4: 3 B2: ='a' B2 now correctly shows 1 because it references A2. 4. select B2:B4 5. press Ctrl+D for Fill Cells Down. alternative steps: 4'. go to B2 5'. drag the fill handle to B3 and B4 alternative steps: 4''. go to B2 and press Ctrl+C 5''. select B2:B4 or B3:B4 and press Enter or Ctrl+V Actual Results: B3 and B4 wrongly also show 1 because they also reference A2. Steps 4'' and 5'' only produce the bug in the first sheet. Expected Results: B3 should reference A3 and show 2. B4 should reference A4 and show 3. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: When you save and reload the file it is correct. Similar to the fixed bug https://bugs.documentfoundation.org/show_bug.cgi?id=105245 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
This seems to have begun at the below commit. e76b8eaeb5cea3fb2cdff12a78c6c70f080b32c2 is the first bad commit commit e76b8eaeb5cea3fb2cdff12a78c6c70f080b32c2 Author: Matthew Francis <mjay.francis@gmail.com> Date: Thu May 28 18:47:00 2015 +0800 source-hash-571070074671bd0102422dd8a0ac1c3be6358f80 commit 571070074671bd0102422dd8a0ac1c3be6358f80 Author: Kohei Yoshida <kohei.yoshida@collabora.com> AuthorDate: Fri Jan 31 15:44:00 2014 -0500 Commit: Kohei Yoshida <kohei.yoshida@collabora.com> CommitDate: Fri Jan 31 15:45:56 2014 -0500 Speed up simple fill of formula cells. Vertical direction only. Other cells could be optimized in a similar fashion, but they aren't that slow even with the current code. Change-Id: I0b71bf271fab68c9fba0b39463dfe3ef46dacfb0 Markus, maybe you're interested, because you fixed bug 105245.
Adding Cc: to Kohei Yoshida
Dear Gilward Kukel, 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
still present Version: 6.4.3.2 (x64) Build-ID: 747b5d0ebf89f41c860ec2a39efd7cb15b54f2d8 CPU-Threads: 4; BS: Windows 10.0 Build 18362; UI-Render: GL; VCL: win;
*** Bug 127269 has been marked as a duplicate of this bug. ***
still repro with 6.3.6.2 winx64 unpar and 7.0.0.0.a0+ linx64 unpar homebrew, works better when copying to single cells (B2 copy, B3 paste, B4 paste), thus only filling / copying to ranges affected? think title should reflect that, think to take #127269 as main and this as dup. reg. detailed description there, think 'critical' as producing wrong data, think reopening #115173, possibly dup, possibly it describes a more general underlying problem and this is only a - reproducible - manifestation of it, add. observation: copying to C3 after B3:B4 produces '=#NAME?B$1' as formula and '1' as value in C3, despite B1 being empty,
Still present. Wrong results (that the user might not even notice) are unacceptable. So please fix this. Thank you. Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: de-AT (de_AT); UI: de-DE Calc: CL
Fixed in LO 7.3 and 7.2.5 thanks to commit 2997c5c2604cd5054710ad35e1e0a9fd18f8ae79 author Eike Rathke on Thu Nov 25 13:34:45 2021 +0100 Resolves: tdf#128914 Create copies for non-shareable token arrays