steps to reproduce: - open two instances of LO Calc, e.g. LO 6.0.7.3 and LO 6.1.4.2 with same locale - LO 6.0.7.3, cell A1: enter =Today() - copy with ctrl+c - LO 6.1.4.2: paste with ctrl+v -> cell A1 shows number (e.g. 43535) instead of expected formula same behaviour if copied from AOO 4.1.5 to LO and vice versa copying from LO into Excel works: - open Excel 2016 - new a spreadsheet - cell A1: paste with ctrl+v - A1 shows =Today() copy from Excel into LO spreadsheet works too, Paste Special shows options: - Microsoft Excel Binary Interchange format (Biff8) - Microsoft Excel Binary Interchange format (Biff5)
Works for me - copy from 6.3 to 6.0.7.3 and vice versa Verze: 6.0.7.3 ID sestavení: 1:6.0.7-0ubuntu0.18.04.2 Version: 6.3.0.0.alpha0+ Build ID: 732d630c3d2a168c725c18e4dd8df7a0a4f85566 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Created attachment 149977 [details] copy and paste formula between lo instances not working for me with LO 6.3 (dev build) and LO 6.1.5.2 (msi installed) - Win 10
Created attachment 149979 [details] Paste special window I can confirm (on Windows 10). In both directions (LO Dev → LO 6.1, LO 6.1 → LO Dev) In attachment, what I get if I use Paste special instead of Paste.
I don't think there are many users having different instances of LibreOffice installed at the same time. Let's change the summary to a more realistic scenario... I can confirm it from AOO 4.1.3 to LO LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 but not the other way around... it works if paste special is used. Reducing severity...
Dear Oliver Brinzing, 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://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
*** Bug 148590 has been marked as a duplicate of this bug. ***
(In reply to raal from comment #1) > Works for me - copy from 6.3 to 6.0.7.3 and vice versa Seems Windows-specific. (In reply to Xisco Faulí from comment #4) > I don't think there are many users having different instances of LibreOffice > installed at the same time. Let's change the summary to a more realistic > scenario... Maybe have both? It's important detail that not only AOO -> LO copy-pasting is affacted, but LO -> LO as well, if for no one else, then to the person who picks up this bug.
Dear Oliver Brinzing, 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