Bug 164341 - Write Error. The file could not be written.
Summary: Write Error. The file could not be written.
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.4.7.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-16 08:38 UTC by achim
Modified: 2025-06-17 13:40 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description achim 2024-12-16 08:38:19 UTC 
Description:
libreoffice complains at startup with the error message "Write Error. The file could not be written.". libreoffice then exits without error message or status.
Sometimes it happens when libreoffice is running, a second headless instance was executed like: "libreoffice -env:UserInstallation=file:///tmp/tst --cat some.tld" and then a new document is opened.

To get rid of the error, all instances of libreoffice must be closed, but then you may run into the problem described in #164332 , means that changes can get lost.

Steps to Reproduce:
1. env TMP=/michgibtsbestimmtnicht libreoffice some.tld


Actual Results:
libreoffice exists

Expected Results:
Should work flawless ;-)
At least an information should be shown how to proceed.


Reproducible: Sometimes


User Profile Reset: No

Additional Info:
The "Steps to Reproduce" are a very simple example, hopefully pointing to the same reason and behaviour as described in "Description".

Additionally I've observerd that sometimes ~/.config/libreoffice/4/.lock was removed after calling "libreoffice -env:UserInstallation=file:///tmp/tst ..."  (but can't reproduce it reliably).

May be this bug is related to #160484 #164332 #164340