https://bugs.documentfoundation.org/show_bug.cgi?id=150450

            Bug ID: 150450
           Summary: DOCX Document Intermittently Appears Saved as a DOC
                    File with DOCX Extension
           Product: LibreOffice
           Version: 7.3.5.2 release
          Hardware: All
                OS: macOS (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Description:
LibreOffice: 7.3.5
Apple iMac: MacOS Monterey 12.5

I downloaded LibreOffice 7.3.5 to try out. Played around a while, seemed fine.

I loaded a 50k DOCX file (created with MAC MS Word 2016) and made changes.
Saved File. Reloaded, all good. Made more changes, Saved. Exited. Later, when I
tried to open, it said (instantly):
“my_file.docx” is damaged and can’t be opened. You should move it to the Trash.

So, I went to a backup (lost my changes) and tried to recreate the issue, but
could not. So, more editing and multiple saves, exited, corrupted again.
So, deciding to create a Bug Report, I tried to recreate the issue for the
report, no dice. Everything works fine.

I noticed that the 50k file, was saved as a 40k file. Just on a whim, I renamed
the file to my_file.doc. Now both Word and LibreOffice load the previously
corrupted file, with no issues.



Steps to Reproduce:
1. LibreOffice 7.3.5
2. Open My_File.docx
3. Make changes to the file
4. Save changes
5. Repeat 3-4 a few times.
6. Exit LibreOffice
7. Double Click the DOCX file
8. Corrupt message occurs

Actual Results:
“my_file.docx” is damaged and can’t be opened. You should move it to the Trash.

Expected Results:
Open/Edit File.


Reproducible: Sometimes


User Profile Reset: No



Additional Info:
It appears that the DOCX decompression occurs before Word or LibreOffice is
opened (since it occurs so quickly after double-click file. It fails, so it
never loads the editor (word or LibreOffice).
Once the issue occurs, both Word and LibreOffice see the exact same issue.
Renaming the file to *.doc allows the file to load correctly.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to