The first thing that comes to my mind is, are you running out of disk space or is there a permission problem on the directory where you are trying to store the file.
journalctl is the command and -b is the option which says view the last boot (-b is the same as -b 0). The system log is called the journal. I tend to lean toward a permission problem, because you’d be having a lot more issues if it were space, but
# check directory permissions
ls -ld DirectoryWhereStoringOdtFile
# check disk space
This is a good insight, I understand a little better why it’s a “write” issue when trying to open something.
The file is saved in my documents folder, the one generated by Linux by default, and I use this folder all the time without issue.
…this is interesting…
So just for sanity’s sake, I tried saving a test document in my documents folder, and the error happened as it always does, and the program crashed, but then I checked my documents folder, and the file HAD saved successfully. I just can’t open it to verify if it actually saved anything into the document or not…
When you open a file for editing, which is what happens unless you open a file for
viewing, lock files are created. One is created in the folder that the opened file is in and in the format .~lock.filename.odt# and one in the user profile as .lock.
These files are to prevent another instance of LO opening and editing the same file.
The lock files are automatically deleted when the file is closed.
It is possible that LO crashed on April 6th and the file in your configuration folder was not deleted. You can possibly check the crash folder in your config if that was the case.
I would troubleshoot by checking owner/permissions on your Documents folder and any others that you would save files in. I would also start with a clean, fresh config folder (profile) Just rename the current config folder and when you launch LO it will create a fresh one.
I was about to try and rename that folder and delete the .lock file and all that, when I had this thought. I tried opening another random document in that folder, an older one that I hadn’t tried previously, rather then just trying to open the same exact one each time, and that one had very similar behavior, except the error was different, something about a .tmp folder or something? Then the screen flashed a bit…and now everything works…
I opened that document, then the one I wanted to open, and it all just works totally normally now…and I have not the faintest idea why…
I think the only thing more frustrating then having a problem I can’t solve is a problem solving itself and not knowing how or why it happened or how to fix it in the future…
Well this is anti climactic and a little embarrassing. Thank you to everyone who tried to help, I’ll definitely come back here if it starts acting up again.