This is on Windows XP. This happens when you start LibreOffice from Windows Explorer by using Windows' file type associations: you double-click on a LibreOffice file in Windows Explorer and it opens that file in LibreOffice. If you then close the file in LibreOffice (but leave the application running), the lock on the file is correctly released, and it can then be deleted, for example. However, LibreOffice retains a lock on the directory from which the file was opened, and, even with the file closed, you cannot delete the directory while LibreOffice is still running. To reproduce: - create a new directory anywhere - copy any LibreOffice file to this directory - with LibreOffice not already running, double-click (or press Enter) on this file - observe the file correctly opens in LibreOffice - close the file in LibreOffice, but leave LibreOffice running - in Windows Explorer, attempt to delete the file you have just opened and closed - observe this happens correctly - now attempt to delete the directory you created - observe that this throws an error ("Cannot delete <dirname>: It is being used by another person or program" on Windows XP) I would suggest that when LibreOffice is started this way, it should not place a lock on the directory from which it is started. Alternatively, if it must place such a lock, it should release it when the file is closed. This problem does not occur if you start LibreOffice from the Start Menu, then open a file either using the LibreOffice menu or via Windows Explorer.
When you start LibreOffice from Windows Explorer by using Windows XP and you have just opened and closed a LibreOffice file. If you then close the file in LibreOffice, but leave the application running, you can not delete the directory. You see the error: "Cannot delete <dirname>: It is being used by another person or program".
Still reproducible on LO 4.0.4.2 & Win7 Home Premium 32bit, not only on XP. Directory/folder still locked by LO though it's empty.
I've experienced a very similar problem accessing files on a Samba share (Samba 3.6.3) on Windows 7 Professional amd64 and using LibreOffice 4.0.5.2. After a reboot if I navigate to the share and open the file, it opens correctly the first time. I then close it, and no lock file remains. Also, running smbstatus on the server does not show the LibreOffice file as being open. However, when I double-click on it again in explorer, I get the warning that it is locked by unknown user. If I instead open LibreOffice and go to File - Open, it opens successfully without the error.
FWIW, the Windows Notepad has the same behaviour. My guess is that this is the "currently active directory" which is never changed after startup. On GNU/Linux (and other Unix clones) it does not matter that much because a used directory can be unlinked (becomes unreachable (invisible) from the filesystem and will automatically be effectively deleted when closed by the last program having it open). With Windows' approach of "refuse to delete something in use", well, this becomes visible.
** 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.3 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-06-08
Sorry, I no longer have access to a Windows machine on which to test this. For anyone who does, it will be /extremely/ simple to do.
Confirmed. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: 437210d58f32177ef1829d704f7f4d2f1bbfbfdd TinderBox: Win-x86@39, Branch:master, Time: 2015-06-18_07:21:56 Locale: fi-FI (fi_FI)
*** Bug 100877 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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 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-20170901
I can't reproduce on Windows 10 with Version: 6.0.6.2 (x64) Build-ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77 CPU-Threads: 8; BS: Windows 10.0; UI-Render: Standard; Gebietsschema: de-AT (de_AT); Calc: group Closing as RESOLVED WORKSFORME. If you still have this problem, please reopen as NEW.
I can solve the problem that you are facing, you just click on this link https://rememberpasswordsinmicrosoftedge.net . Here is the best solution because i personally use this when i was facing the same issue.
Thank you for sharing your details and experience http://dvdplayerwindows10.com I think it very good for me.