Created attachment 93956 [details] A small spreadsheet that can be used to reproduce the problem Problem description: Steps to reproduce: Use the attached spreadsheet. It is in Swedish but that doesn't matter. I use the Swedish language pack so my instructions below are my guess of what the text in English would be (e.g. Paste contents ...). 1. Select row 9 and copy it (ctrl-C). Cell E10 contains '=G$22' 2. Right-click on row 10 and select Paste contents ... 3. Select Paste all plus Move cells downwards Current behavior: 4. Cell E10 now contains '=G$22' which was correct at the time it was copied but not after insertion of the new row. Expected behavior: 5. I expect cell E10 to be the same as E9, i.e. '=G$23' Contents of E9 is adjusted for the inserted row. Operating System: Ubuntu Version: 4.1.3.2 release
Confirmed Ubuntu 13.10 LibreOffice Master built today New Minor - can slow down professional quality work (not prevent though) Medium - usually "low" but this seems like it could potentially cause enough problems to bump it up @Seved - do you know if this was always broken? If it's a regression we might be able to bibisect it and figure out what broke it.
** 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 (4.4.2 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
Yes, the problem is still there. However, the obvious workaround is to first insert an empty line and then copy the source line to the newly created line without movement. Then the copy is correct. This has very low priority for me and you may select to discard this report if you want. I guess that it is difficult to find such absolute references and decide to change them in such a specific case. In my earlier work we use bugzilla and could mark some reports as "won't fix" which would probably be adequate in this case. /Seved
Now I have also checked with Open Office 3.2.0 that I had installed on another computer: yes the error was there. Apache Open Office 4.1.1 has the same problem. Gnumeric does not have this feature, (paste and move). Microsoft Office does not have this feature, (paste and move). Normally I use the latest version of LibreOffice with support for Swedish, which now is Version: 4.4.2.2 Build ID: 40m0(Build:2) Språkinställning: sv_SE Operating system Ubuntu 15.04 or Ubuntu 14.04 LTS (on another computer). Sometimes I use Windows Vista or Windows 8.1
@Seved Torstendahl - thanks for the great feedback. We won't close as WONTFIX as it's a valid bug but it's noted that it's low priority :) We'd love to see you in the chat http://webchat.freenode.net/?channels=libreoffice-qa We're a friendly bunch that needs all the help we can find. No developer skills needed, mostly just patience and a desire to help :)
** 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.5 or 5.2.1 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-20160920
Yes, the bug is still there, LibreOffice 5.1.4.2, Build ID: 1:5.1.4-0ubuntu1 on Ubuntu 16.04. Please see comment#3 and comment#4 which are still valid: - easy to work around, - very special case Regards Seved
** 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
The bug is still there with Ubuntu 18.04.1, LibreOffice version Version: 6.0.6.2 Build ID: 1:6.0.6-0ubuntu0.18.04.1 CPU-trådar: 2; Operativsystem: Linux 4.15; UI-rendering: standard; VCL: gtk3; Språkinställning: sv-SE (sv_SE.UTF-8); Calc: group As I said in comment 3, 4 and 7 this is of very low priority, and is easy to work around PS I noticed now that the bug description is incorrect. The line "1." should be: "1. Select row 9 and copy it (ctrl-C). Cell E9 contains '=G$22' " ie. cell E9, not cell E10
Dear Seved Torstendahl, 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
The bug is still present in LibreOffice Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.10 CPU-trådar: 8; Operativsystem: Linux 4.15; UI-rendering: standard; VCL: gtk3; Språkinställning: sv-SE (sv_SE.UTF-8); Calc: group As I have pointed out earlier this is not important as it is easy to circumvent.
Reproduced with comment 9 Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: eb6127e9aba2ad19cc5ad5c00ed4c67c5ee301af CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Dear Seved Torstendahl, 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
Version: 7.3.7.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: sv-SE (sv_SE.UTF-8); UI: sv-SE Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.2 Calc: threaded Yes, the problem is still there but my comments 3 and 4 earlier are still valid: easy to circumvent so don't spend energy on fixing it!