Not sure if what may be a corrupted file is considered a bug but the only reason I am reporting this is due to what can and can't be done with the file as reported below. I.E. Using Linux it is reported as locked when no ~lock file exists but can be opened Read Only but on MACOS it's reported corrupt and can't be accessed at all. On the Linux system there is no ~lock file associated with that file anywhere. I used find -exec -alhd {} \; and grep'd for it all over the Linux system and checked using lsof, ps for other instances of office running, stuck processes, etc. nothing. So then using Linux command line renamed the file (mv) and tried to open it, no instances of office were running, tried to open the file and it still said the renamed file was locked by Unknown user. That rules out a ~lock file because of the name change. What I landed up doing was opening the renamed file Read Only then saving it as its original name. That restored access to the file but it did not determine the root cause of the problem so as to prevent it from happening again. The file is on a NAS and the above occurred on a openSuSE system where the file is accessed from exclusively. My MacBook also has access to that share so just to see I tried to open the renamed file there using LibreOffice and I got a "Read Error. Data could not be read from the file." So possibly something is wrong with the file but like I said I was able to open it Read Only and then successfully save it. I then copied the renamed file to my MacBook's Desktop and tried to open it there. LibreOffice popped up a message saying the file was corrupt do I want to fix it, I answered yes but Libreoffice was unable to fix it. If this is something deemed looking into I can provide the file. The MACOS LibreOffice version is 7.3.6.2 the openSuse version is older.
Please attach the file. Thank you.
Seven months later you finally ask for the file? I don't know if I have it let alone what it was named... I think I'm even on a newer version of Libre Office. Nice racket you got going here, let it sit for eons and hope it goes away... Well you lucked out, it did... Nice work...