Description: When you cut a cell and insert a row in the sheet before pasting the cell, references are not updated and resulting formula is invalid Steps to Reproduce: 1. Create A1→"100", G10→"=A1*2" 2. Verify that G10 gives 200 3. Cut G10 4. Insert row below line 1 5. Paste into D20 Actual Results: D20 → "=#REF!11" Expected Results: D20 → "=A1*2" Reproducible: Always User Profile Reset: No Additional Info: Works well if cut cell is B2 (strange). User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0
My formula in D20: =A11*2 Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha0+ Build ID: 1fce5b024e9f25c3fcef2537a22474ece0dc416f CPU Threads: 8; OS Version: Linux 4.8; UI Render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on December 10th 2016 Arch Linux 64-bit LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
** Please read this message in its entirety before responding ** 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
Versione: 6.1.0.1 Build ID: 378e26bd4f22a135cef5fa17afd5d4171d8da21a Thread CPU: 2; SO: Linux 3.16; Resa interfaccia: predefinito; VCL: kde4; Versione locale: it-IT (it_IT.UTF-8); Calc: group threaded (https://gerrit.libreoffice.org/gitweb?p=core.git&a=log&h=378e26bd4f22a135cef5fa17afd5d4171d8da21a) Default settings (clean config) I confirm I can reproduce this bug. But, isn't it the normal behaviour of Calc that, when you copy a cell, referring to another cell, the references got updated accordingly and, if you paste the cell too far to the left (or above) the pasted cell, you end up pointing to a non-existent cell? I.e. for example in case 1, D20 should finally be pointing to {A-6position to the left}{1+10position to the bottom} that is #REF!11 and, for case 2, if I have 1 in A1 and =A1 in B2 if I copy-paste B2 in B1 I got =#RIF!1 (as I would expect); if I copy-paste B2 in D20 I got 0 (i.e.: =C19)... Should it be normal (as I thought) or should default behaviour be different?
Hmm, it seems Ascaf is right and actually I get the *same* result now without any row insertions! That is, =#REF!20*2 after pasting in D20. A similar result is indeed seen in any paste to the left of G column. Let's close.
> But, isn't it the normal behaviour of Calc that, when you copy a cell, Yes, but the report is not about copying. It is about cutting. So, this is the formula in D20 after the following procedures: A. Cutting G10, no row insert, paste in D20: =A1*2 B. Cutting G10, row 2 insert, paste in D20: =#REF!11*2 C. Copying G10, no row insert, pate in D20: =#REF!11*2 D. Copying G10, row 2 insert, paste in D20: =#REF!11*2 Cases C and D are about copying and are consistent. Cases A and B are about cutting and are inconsistent. In case B, "cut" is adopting "copy" behavior. I think this is the intent of the original bug report.
Indeed, sorry for sloppy testing back there.
Thanks for the explanation. So I thought it might be interesting to check the clipboard while doing the usual sequences and to see if the inconsistencies were triggered by action different from adding row. In particular I got this (below, with klipper I mean the values stacked in the clipboard, newest to the right): IN new spreadsheet: A1 --> 100 g20 --> =A1*2 (200) g20 --> ctrl-x klipper: 200 (the value on the clipboard stack) d20 --> ctrl-v now d20 is 200 (=A1*2) klipper: 200 (unchanged) d20 --> ctrl-v (accept overwriting) now d20 is #RIF! (=#RIF!11*2 like if cutting-pasting) klipper: 200, #RIF! (the same value you'll get if you copy-paste instead of cutting-pasting) keep on overwriting (if you want) but the value will not change any more) for comparison with copy-paste IN new spreadsheet: A1 --> 100 g20 --> =A1*2 (200) g20 --> ctrl-c klipper: 200 d20 --> ctrl-v now d20 is #RIF! (=#RIF!11*2) klipper: 200, #RIF! (the value pasted has been updated, in accordance with the internal rules, I suppose) So it seams the simple action of pasting twice triggered some formula updating to the clipboard?
(In reply to Ascaf from comment #7) > Thanks for the explanation. So I thought it might be interesting to check > the clipboard while doing the usual sequences and to see if the > inconsistencies were triggered by action different from adding row. > In particular I got this (below, with klipper I mean the values stacked in > the clipboard, newest to the right): > > IN new spreadsheet: A1 --> 100 > g20 --> =A1*2 (200) > g20 --> ctrl-x > klipper: 200 (the value on the clipboard stack) > d20 --> ctrl-v > now d20 is 200 (=A1*2) > klipper: 200 (unchanged) > d20 --> ctrl-v (accept overwriting) > now d20 is #RIF! (=#RIF!11*2 like if cutting-pasting) > klipper: 200, #RIF! (the same value you'll get if you copy-paste instead of > cutting-pasting) > keep on overwriting (if you want) but the value will not change any more) > > for comparison with copy-paste > IN new spreadsheet: A1 --> 100 > g20 --> =A1*2 (200) > g20 --> ctrl-c > klipper: 200 > d20 --> ctrl-v > now d20 is #RIF! (=#RIF!11*2) > klipper: 200, #RIF! (the value pasted has been updated, in accordance with > the internal rules, I suppose) > > So it seams the simple action of pasting twice triggered some formula > updating to the clipboard? Sorry above read g10 instead of g20: IN new spreadsheet: A1 --> 100 g10 --> =A1*2 (200) g10 --> ctrl-x klipper: 200 (the value on the clipboard stack) d20 --> ctrl-v now d20 is 200 (=A1*2) klipper: 200 (unchanged) d20 --> ctrl-v (accept overwriting) now d20 is #RIF! (=#RIF!11*2 like if cutting-pasting) klipper: 200, #RIF! (the same value you'll get if you copy-paste instead of cutting-pasting) keep on overwriting (if you want) but the value will not change any more) for comparison with copy-paste IN new spreadsheet: A1 --> 100 g10 --> =A1*2 (200) g10 --> ctrl-c klipper: 200 d20 --> ctrl-v now d20 is #RIF! (=#RIF!11*2) klipper: 200, #RIF! (the value pasted has been updated, in accordance with the internal rules, I suppose)
Dear libreoffice, 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
Repro Version: 7.2.0.0.alpha1+ / LibreOffice Community Build ID: 98a8d8bc15018576e1312493425d7bb3725be735 CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: x11 Locale: de-CH (en_US.UTF-8); UI: en-US Calc: threaded
Dear libreoffice, 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
The problem is that Calc knows how to do "cut" and _immediately_ _one_ "paste", but does not know how to do the _same_ _exact_ "paste" if that action is not immediately after the initial "cut". Any "paste" action that is not the first and immediate action after the initial "cut" action will work as "(copy+)paste". This is also true for several (adjacent, vector) cells selected at once for pasting in the first immediate step – only the first pasted cell will have the same exact formula, whereas the others will behave as copy+paste. So, in Calc, when doing cut, insert (cells), paste, the resulting paste is not the same as cut and paste, but rather a copy and paste. And when repeating the first immediate paste after the initial cut, the result is also not the same as the first paste, but rather it works as a "copy+paste". Example: 1. A1: 100 2. B2: =A1*2 3. Cut B2. Note the surrounding "ants" around B2. 4. First immediate paste on D3. Result: =A1*2. Note the surrounding "ants" around B2. 5. Paste on E3. Paste on D4. Paste on B3. Note that the resulting formulas are equivalent to copying the initial B2 (still surrounded by "ants") and then pasting that on E3, D4 and B3 respectively. 6. Paste on A3. The behavior is exactly the same as step 5. With the current behavior, there is no alternative but to result in =#REF!2*2. In order to repeat the same formula several times in Calc, there are a couple of options: either use absolute references before cutting, or you have to cut the formula itself from within the input window formula bar. Unfortunately, in the second case the corresponding paste action(s) will only paste the formula, not the cell's format. Other spreadsheet tools might work differently. One possibility is to transform this report into a request for enhancement (or starting a new one), allowing to paste the initially cut cell multiple times "as-is", or even when other non-clipboard actions are performed in between.