Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Mint 20.3 MATE, Android, Windows 10, MX Linux and Mint 21.1 MATE
Posts: 1,052
Rep:
Libre Office won't save or save as...
I am using Mint 20.2 and Libre Office, which opens a document from my memory stick but when I modify it and want to save, it reads an error:
Quote:
Error saving the document resume 2022:
Write error.
The file could not be written.
Then
Quote:
OK.
To save as, I have to start a recovery of the document with the original title.
Below is the the title of the document that comes up, it should only be Brendan MB Resume.docx
The lock file is used to prevent multiple users from editing the same file at the same time. It should be deleted when the document is closed but a crash or other glitch might not have when previously opened.
With the document closed try deleting the lock file and see what happens. Otherwise:
As posted the flash drive might be mounted read only.
The document might be set to read only by LO.
The flash drive might be failing and mounting read only.
Distribution: Mint 20.3 MATE, Android, Windows 10, MX Linux and Mint 21.1 MATE
Posts: 1,052
Original Poster
Rep:
Quote:
Originally Posted by michaelk
The lock file is used to prevent multiple users from editing the same file at the same time. It should be deleted when the document is closed but a crash or other glitch might not have when previously opened.
With the document closed try deleting the lock file and see what happens. Otherwise:
As posted the flash drive might be mounted read only.
The document might be set to read only by LO.
The flash drive might be failing and mounting read only.
Can you copy the document to your hard drive?
I saved an image from my SSD to the stick and it opened. And I copied a document to SSD and it opened. I don't know how to see if LO is set to read only?
I tried making a document called test save and save as docx and this results in LO wanting to recover another document, "untitled 1" if I choose to recover it it opens and has the test page in it and is still untitled even though this time it was titled in save as as "test 3".
I renamed the file without lock... but there is only the one line in that when opened.
If you can copy files to the flash drive then it isn't read only. If a document opens read only there will be a banner at the top indicating it is read only.
Did you create the new test document on the SSD or the flash drive? LO will use default naming "untitled X" when a new document is saved unless it is renamed and also defaults to ~/Documents.
Check your backup directory for files. For the location look at the tools->options backup path. This is where recovery files are located. Typically LO is configured to auto save files every 10 minutes. Seems strange that LO wants to recover the file.
With LO not running just delete the lock file. The file contents from the OP "03.08.2022" indicates the date the lock file was created so was this the last time you opened this particular file?
Distribution: Mint 20.3 MATE, Android, Windows 10, MX Linux and Mint 21.1 MATE
Posts: 1,052
Original Poster
Rep:
Quote:
Originally Posted by michaelk
If you can copy files to the flash drive then it isn't read only. If a document opens read only there will be a banner at the top indicating it is read only.
Did you create the new test document on the SSD or the flash drive? LO will use default naming "untitled X" when a new document is saved unless it is renamed and also defaults to ~/Documents.
Check your backup directory for files. For the location look at the tools->options backup path. This is where recovery files are located. Typically LO is configured to auto save files every 10 minutes. Seems strange that LO wants to recover the file.
With LO not running just delete the lock file. The file contents from the OP "03.08.2022" indicates the date the lock file was created so was this the last time you opened this particular file?
The program open anew from SSD and won't save a test document.
On another Linux computer it works. But the renamed files still don't produce more that the line with the date.
Back up seems empty.
That date is the one.
Renaming the files and then opening them doesn't make a difference.
Starting anew, the document will just be in RAM until it auto saves i.e. after 10 minutes by default or if you save the document. You did not post where you were trying to save the document. The recovery message when you try to save the test document is strange since the backup directory is empty. It appears like you can copy files back and forth between the flash, SSD or maybe from other sources so filesystem corruption or either file system being read only is not the problem? I assume you have sufficient free space on either filesystem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.