Description: After opening a document as a copy, LibreOffice appears to treat it the same as a completely blank untitled document. To keep your LO windows uncluttered, when you open a document, LO will attempt to reuse a completely blank unmodified document that you currently have open. Since you have made no changes to it, it will close your unmodified document and taking over that window. Unfortunately, when you open a document as a copy, LO apparently isn't setting a modified flag, so LO treats it exactly as it would a blank document. It reuses the window and clobbers your copy. Steps to reproduce: 1. Open a file as one user 2. Attempt to open the same file as another user 3. Choose "Open Copy" 4. Immediately do File->Open and open another document (as second user) Expected: Both the copy of the file in use and the new file should be open, in different windows. Actual: The copy has been completely lost with no way of easily reopening it. Because it actually opened the new document, it closed our copy with no way to undo. And because of bug 85325, it doesn't even show up under recent documents. It's easy to work around once you know what's happening. Simply insert a space or make any type of modification to your document, and it will be safe from clobbering. Unfortunately, this bug has been around since before LO. I was able to reproduce this using OpenOffice 3.2.1, so I'm setting the version to Inherited from OOo.
Never noticed this before, but I can confirm it happens under LO 4.3.4.1 under RHEL 6. Had to open a document that someone else was working on, or with OS permissions set to read only to simulate it so I could open it as a "copy".
** 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.0.4 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 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-12-20
** 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-20170103
I tested this again with LO 5.3.0 and wasn't able to reproduce anymore. I believe this bug went away when the option to "Open Copy" disappeared. LO now opens the document as read only and prompts users to enter edit mode. Since I don't know exactly which version fixed it, I'll mark this RESOLVED:WORKSFORME.