Bug 1043312

Summary: Libreoffice .doc and .docx formats are seen by MS Office as corrupted and not able to be opened
Product: [Fedora] Fedora Reporter: Terry Duell <tduell>
Component: libreofficeAssignee: Caolan McNamara <caolanm>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 19CC: caolanm, dtardon, erack, ltinkl, mstahl, sbergman, tduell
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-25 13:22:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Terry Duell 2013-12-15 22:25:33 UTC
Description of problem:
.doc and .docx format files exported, are reported by MS Office 2010 to be corrupt and cannot be opened. Recipient has also tried Goggle docs and it also reports files as corrupted.

Version-Release number of selected component (if applicable):
Build ID 4.1.3.2-11.fc19

How reproducible:
Not sure, haven't had time test fully. 

Steps to Reproduce:
1.load .doc file from MS office.
2.edit file
3.save file as .doc or .docx and send to MS Office

Actual results:
.doc and .docx files cannot be opened in MS Office

Expected results:
.doc and .docx files will be opened and rendered correctly in MS Office

Additional info:
These are business documents, and recipient doesn't have the time to allow me to conduct additional tests to further isolate the cause of the problem.
Prior to this version of LO, .doc and .docx files were being passed to and from this recipient and being read and edited without problems in both MS Office and LO (in the past couple of weeks).
The file can be saved as pdf and is read OK by pdf reader.

Comment 1 Terry Duell 2013-12-16 04:38:50 UTC
Unfortunately I can't provide the file that is showing the problem. It is quite a large .doc, generated in MS Office 2010, and contains two large tiff images as well as text, tables and small jpeg images. It is about 2.4 MB.
I know none of this is much direct help.
I have tried generating a small .doc here in LO, and uploading it to Google Docs and then loading it to edit, and it is OK.
Checking again with the recipient of the file that gave the trouble, the advice now is that the file can be uploaded to Google Docs, and viewed, but when "open with > Google Docs" is selected, it attempts to load then fails. Also fails to load into MS Office 2010, with a message they say mentions "corrupted".
Sorry can't be of much more help. I don't have MS Office here to check.
Please let me know if there is anything I can do to help home in on this problem.

Comment 2 Caolan McNamara 2013-12-18 11:08:11 UTC
So, this doesn't happen with a new fresh document that you generate yourself, right ? It only happens with some documents you've got but can't attach here. If you are in a position to email them to me to test this then please do.

Comment 3 Terry Duell 2013-12-18 20:19:24 UTC
I can't reproduce the problem with a doc I generate with LO, and I haven't seen this problem previously with docs generated by MS Office that have been passed to me for edit, but LO has been updated in the meantime.
I suspect there is something in this particular MS office generated doc that causes a problem after it has been through LO.
I'll see if the doc can be made available.

Comment 4 Terry Duell 2013-12-21 01:05:04 UTC
I have tried editing the doc file that causes the problem, to remove any confidential material, but the resulting file uploads to Google Docs OK and can be opened for editing.
Looking back at the sequence that led to the problem file, it seems that using LO to 'record' and 'show' changes and then adding some text, are the only things that happened on LO, and the saved .doc and .docx versions of the edited file were then unable to be opened in MS Office, or opened for editing in Google Docs.
Hope this helps.

Comment 5 Caolan McNamara 2014-02-25 13:22:29 UTC
can't really fix this without knowing the exact problem. Its presumably a duplicate of one of the more specific known issues.

Comment 6 Terry Duell 2014-02-25 21:15:27 UTC
OK. It is unfortunate that I can't provide the offending document.
Thanks for your help.