Thanks Paul,
There are some ".~lock...#" files, but not many. I'm pretty sure more
files than that are asking for recovery.
Also, I notice the lock files have filenames in them, that refer to
files under .config, which don't get synced by Nextcloud. Is that likely
to be a problem?
Cheers,
Richard
On 18/08/25 11:03, Paul D. Mirowsky wrote:
Have you checked for "~lock" files on local and Nextcloud?
On 8/16/25 06:06, Richard Hector wrote:
Hi all,
I'm seeing a problem where apparently every (.docx?) document needs
recovery on opening. I don't believe these documents were the result
of a crash, which is what Writer is suggesting. If I try to recover,
the recovery fails.
Background:
My father finally got sick enough of MS to ask me to set him up with
Linux.
I built him a Debian 12 box, with LO, to experiment with, and he said
he was happy with it. He was already using Nextcloud to sync his
files, because that seemed the easiest way to back up his Windows
machines. That made it relatively easy to sync to the new Debian box
as well, so all his files were available.
The initial system seemed to be able to open MS and other documents fine.
Then recently I upgraded his laptop from Windows 10 to Debian 12,
because he's getting on a bit and wasn't getting out of his chair to
go and use a desktop ...
Now, when he tries to open documents on the new machine, LO says they
need recovery. This seems to apply to all docx files, though I haven't
done an exhaustive search. I tried on the desktop, and the problem now
exists there too. I'm pretty sure it didn't before, though as I say it
didn't get much use.
So I suspect most of these files were as saved by MS Word, but some
may have been saved by LO.
I did a web search, and found some stuff about this kind of thing, but
it dates back a bit - I think it appears in the 2011 - 2014 range.
Any suggestions?
Should I 'discard the recovery data', which seems to be the only option?
Are the files actually corrupt? Is there a LO bug? Has Nextcloud left
something behind that's triggering this?
Is there a way to fix all the files at once, (eg a commandline program
from 'find'), if that's what's needed?
Cheers,
Richard
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.