Bug 152914 - Writer reports ALL .odt files as corrupt, even newly saved ones.
Summary: Writer reports ALL .odt files as corrupt, even newly saved ones.
Status: RESOLVED DUPLICATE of bug 60909
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.3.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-07 16:28 UTC by Stirling Westrup
Modified: 2023-01-23 03:22 UTC (History)
1 user (show)

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 Stirling Westrup 2023-01-07 16:28:30 UTC 
Description:
LibreOffice refuses to open any .odt files, saying they are corrupt. It offers the choice of fixing them, which never succeeds.

Steps to Reproduce:
1. Save a trivial test file from Writer
2. Close Writer
3. Attempt to open file. Its reported Corrupt

Actual Results:
File is reported corrupt. Even zero-length files. After an attempted repair, the zero length file was 4.2 KB, and was still reported corrupt.

Expected Results:
Saved files should be loadable.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
I'm not sure when this bug showed up but I suspect its very new. I hadn't noticed it before yesterday's software update (I'm running OpenSUSE Tumbleweed 20230105) but I know the bug was NOT present in 7.4.1.2

Version: 7.4.3.2 / LibreOffice Community
Build ID: 40(Build:2)
CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb)
Locale: en-CA (en_CA.UTF-8); UI: en-US
Calc: threaded
Comment 1 Stirling Westrup 2023-01-07 16:48:23 UTC 
Okay, I've found the cause of this bug. OpenSuse recently changed its use of /tmp to tmpfs and now /tmp regularly fills to 100%. When this happens many things break, including LibreOffice's loading of files. It would be helpful if it could detect that /tmp was out of space rather than just report corrupt files.
Comment 2 raal 2023-01-22 13:12:09 UTC 

*** This bug has been marked as a duplicate of bug 60909 ***