I was working with the spreadsheets and noticed this little gem. The value in the formula with the anchored cells (e.g. $A$1) are updated when i cut and paste in unrelated rows. Steps to reproduce: Enter value 1234 in cell A1 Enter values 5,2,3 in cells A3, A4 and A5 respectively Enter formula ($A$1-ABS(A3))*-1 in cell B3 Drag the formula to fill other 2 cells Now you have values -1229, -1232 and -1231 in cells B3, B4 and B5 Enter values 2, 3, 4 in cells A7, B7 and C7 Select these cells and cut them. Click on A7 cell Paste special: Number and Transpose checked, Operations: None, Shift Cells: Don't shift Values in cells B3, B4 and B5 change to 2, 0 and 1 respectively Formulas are updated to ($A$7-ABS(A9))*-1, ($A$7-ABS(A4))*-1, ($A$7-ABS(A5))*-1 in those cells. I am running opensuse 12.1 and official repository and Build ID: 350m1(Build:413) This also happens on Windows OS
Thank you for reporting this issue! I have been able to confirm the issue on: Version 4.0.4 Platform: Bodhi Linux 2.2 x64 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + As I've been able to confirm this problem on an earlier release I am changing the version number as version is the earliest version that we can confirm the bug, we use comments to say that the bug exists in newer versions as well. Marking as: New (confirmed) Major - loss (change) of data High - default seems appropriate Indeed - quite the gem ;) Thanks for catching this + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
I suggest the interim solution to disable "Paste Special" after cutting cells. The advantage is obvious: Loss or change of data are avoided. I experienced the consequences of this bug in a complex spreadsheet. The changes of links can be difficult to detect and to fix again. I do not see substantial disadvantages of disabling "Paste Special" after cutting cells because formula links are not shifted as expected after cutting and inserting with "Paste Special". I reported this unexpected behaviour with bug 71058 "EDITING: Cut and paste special does not shift formula links as expected". If cells are cut and then pasted normally (i.e. with "Paste" instead of "Paste Special"), all formula links to these cells point to the new cell positions after pasting the cells. This expected shift of formula links does not occur with the command "Paste Special". Formula links still point to the old positions of the moved cells. Therefore, "Cut" and "Paste Special" leads to the same result as "Copy" and "Paste Special" with subsequent deletion of the old cells. Thus disabling "Paste Special" after cutting cells does not lead to a loss of functionality. It can be replaced in the workflow by "Copy" and "Paste Special" with subsequent deletion of the old cells. A loss of functionality occurs only if bug 71058 can be fixed by aligning the behaviour of "Paste Special" with "Paste" after cutting cells. MS Excel 2007 does not offer the full set of "Paste Special" options after cutting cells either. I do not have access to later Excel versions.
(In reply to comment #2) I received a comment to bug 71058. The comment implies that my suggested interim solution has disadvantages, because "Cut" and "Paste Special" behaves as expected unless "Transpose" is selected. Therefore, disabling "Paste Special" completely after cutting cells would disable expected behaviour as well. Alternatively, only the "Transpose" option in "Paste Special" could be disabled as interim solution. However, such a quick fix lacks charm admittedly. Maybe there is no convincing interim solution.
This is a bug. and an old one... I clarified the summary - quite essential to mention Paste special and Transpose to help people seeing the issue :) thanks, Cor
Tell me if I should open a separate bug for this, but it looks to me that formulae are changed when you simply do Cut / Paste (recorded in the undo history as Cut / Move) so this is a more serious problem than it may seem on first sight of the title. I fell foul of this when moving some data around in a simple 'row total' sheet with a protected column of formulae. "Imagine my surprise" when cut / pasting some of the data changed the formulae in unpredictable (by me) ways! Here's how counter-intuitive it is (no need to protect the formulae for this) 1) create a simple 'row sum' table as follows 1 2 =A1+B1 3 4 =A2+B2 2) This displays as expected: 1 2 3 3 4 7 3) Select cells A2 and B2 and cut, gives what you'd expect: 1 2 3 0 4) Click on A1 and paste 3 4 7 7 And C2 now has =A1+A2 - NOT what I expected! I guess this sort of spreadsheet is fairly common and it really had me confused. I can only move my input values around using select, copy, paste, select, delete instead of the obvious select, cut, paste. This seems to be a problem arising from assuming that every cut and paste is a move whereas it is often, and more obviously, just a cut and paste! Surely to get a move you should ask for it via Paste Special? Note that exactly the same table in Writer gives the expected result: 3 4 7 0 and leaves the formula in B3 alone.
Hi Peter, Please, open a new bug report. What you describe is another problem. Best regards. JBF
Another example reproducer - https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1388491
I have also hit this bug using libreoffice-calc 1:4.2.8-0ubuntu2 on Ubuntu 1:4.2.8-0ubuntu2 on x86_64.
(In reply to satphil from comment #8) > I have also hit this bug using libreoffice-calc 1:4.2.8-0ubuntu2 on Ubuntu > 1:4.2.8-0ubuntu2 on x86_64. Sorry, should have read: on Ubuntu 14.04.2 LTS, Trusty Tahr on x86_64.
Created attachment 119968 [details] example sheet
** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20161108
(In reply to QA Administrators from comment #11) The bug is still present (LibreOffice 5.2.3.3, 32-bit version, Windows 10).
*** Bug 104731 has been marked as a duplicate of this bug. ***
** 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
Repro in 6.2+.
Dear alexjironkin, 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 6.4+
yes it's still there and it is an especially embarassing problem when data management in a spreadsheet goes berserk. Of course the specific actions that make the bug emerge are rare, but once a user happens to meet it, trust in all computations will be severely tarnished, and anguish will set in... often reason enough to move to other software... Please anyone who could fix this, help!
Confirmed Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: 4f7bc49bce261f1cf206d25f0299fd080a9f5d28 CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
I've found the problem. Working on a solution.
I've submitted a patch: https://gerrit.libreoffice.org/c/core/+/115535 Waiting for review
scito committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/de4c23fb38a7848e1030075b9c15cbb5c558694c tdf#68976 cut paste transposed: fix wrong position in clipdoc It will be available in 7.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Roland, please mark this bug as resolved. I will mark as Verified later, it ok now. Thanks for fixing. Version: 7.2.0.0.alpha1+ / LibreOffice Community Build ID: 42d2b2d55a27f11153ea1713737d93540a19211d CPU threads: 4; OS: Linux 5.8; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
(In reply to BogdanB from comment #23) > Roland, please mark this bug as resolved. > I will mark as Verified later, it ok now. Thanks for fixing. Thanks for testing. This bug caused a regression for notes and patterns. I fell in my own trap. In my unit tests, my test sample started in A1, i.e. a special case. I've found the problem and I'll submit a patch after https://gerrit.libreoffice.org/c/core/+/116073/9 is merged. After, this regression is fixed, I'll set bugs 68976, 71058, 142065, 142201 together to RESOLVED FIXED.
I've submitted a patch: https://gerrit.libreoffice.org/c/core/+/116501
scito committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/c82d96da1c9a03e1742f2f5a7a93b9993c96a0a0 tdf#68976 fix paste transposed regression for notes/patterns It will be available in 7.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Great! You solved it! I tested again and it is ok in Version: 7.2.0.0.alpha1+ / LibreOffice Community Build ID: ec629c5ee22d02f99d66a5cf975ce239876b7f4d CPU threads: 4; OS: Linux 5.8; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded