Prepare a drive (usb), copy one writer file and generate a big file, Windows Powershell command: [io.file]::Create("<Drive>:\bigblob.txt").SetLength((gwmi Win32_LogicalDisk -Filter "DeviceID='<Drive>:'").FreeSpace).Close after that free space is 0 Kb. Then open the writer file, in this case you get no message, then close the file without save, and reopen you get the Message-Dialog. When you try to save the document you get the Message-dialog immediately Message-dialog: |--------------------------------------------------------------------| | Document in Use | |--------------------------------------------------------------------| | Document file 'test.odt' is locked for editing by yourself on a | | different system since | | | | Open document read-only, or ignore own file locking and open the | | document for editing. | | | | | Open Read-Only | | Open | | Cancel | | |--------------------------------------------------------------------| This message is in this case wrong and confused the user. The problem is the lock-file was create with space 0, but after closing this lock-file would not be remove.
Not getting the message at all. Confirmed free space == 0. Win 7 Pro 64-bit, Version: 5.3.1.2 (x64) Build ID: e80a0e0fd1875e1696614d24c32df0f95f03deb2 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Layout Engine: new; Locale: fi-FI (fi_FI); Calc: CL Version: 5.4.0.0.alpha0+ (x64) Build ID: 1f73ac90da31b62ccf6f040c68e5c0150171240f CPU threads: 4; OS: Windows 6.1; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2017-04-20_07:32:30 Locale: fi-FI (fi_FI); Calc: CL
Hi Buovjaga i can reproduce the error under Linux and Windows (current master 1807db242a09). Here a other Test scenario for Windows and Linux: - Open an document and copy the lockfile - Close LO - Copy the lockfile to the origin lockfile name - Remove the content of the lockfile (you get a 0 Byte lockfile) - Start LO and open the document again. Now you get the above message, this is the same scenario as above, but here you set the lockfile, otherwise it is the same when no space is left
(In reply to Juergen Funk (CIB) from comment #2) > Hi Buovjaga > > i can reproduce the error under Linux and Windows (current master > 1807db242a09). > Here a other Test scenario for Windows and Linux: > - Open an document and copy the lockfile > - Close LO > - Copy the lockfile to the origin lockfile name > - Remove the content of the lockfile (you get a 0 Byte lockfile) > - Start LO and open the document again. > > Now you get the above message, this is the same scenario as above, but here > you set the lockfile, otherwise it is the same when no space is left Repro. Win 7 Pro 64-bit, Version: 5.3.1.2 (x64) Build ID: e80a0e0fd1875e1696614d24c32df0f95f03deb2 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Layout Engine: new; Locale: fi-FI (fi_FI); Calc: CL
Juergen Funk committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=6ca3b3648e25ae9d4d2d29a0df83349198ec3f5e tdf#106942 Wrong message when lock file is empty or corrupt It will be available in 5.5.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Juergen Funk committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=af9bea21390800e5bbc73e07ce9828189d8dabf3 Improve tdf#106942: always erase empty/corrupt lockfile It will be available in 6.0.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Polite ping: is this bug fixed? if so, please close it as RESOLVED FIXED
Hi Xisco Faulí, it is fixed, but the dialog-texts only in english, the other language should be translate, and not forget the text in "uui/source/lockfailed.src" "STR_LOCKFAILED_MSG" is improve