Bug 69607 - FILESAVE: LO exports a corrupted DOCX
Summary: FILESAVE: LO exports a corrupted DOCX
Status: RESOLVED DUPLICATE of bug 65836
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.0.0.alpha0+ Master
Hardware: Other All
: medium major
Assignee: Nikhil Walvekar
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-20 14:16 UTC by Adam CloudOn
Modified: 2013-12-02 11:32 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
original DOCX that is exported bad by LO (43.38 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2013-09-20 14:16 UTC, Adam CloudOn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Adam CloudOn 2013-09-20 14:16:41 UTC
Created attachment 86181 [details]
original DOCX that is exported bad by LO

Problem description:
When loading the attached DOCX into LO, and saving back to DOCX - the exported DOCX is corrupted and cannot be opened by MS Word.

Steps to reproduce:
1. Load the attached DOCX in LO.
2. Save as NEW.DOCX
3. Load the NEW.DOCX in Word
4. File is corrupt

Current behavior:
LO exports a corrupted DOCX

Expected behavior:
LO should not export a corrupted DOCX
              
Operating System: All
Version: 4.2.0.0.alpha0+ Master
Comment 1 Thomas van der Meulen [retired] 2013-09-29 07:12:46 UTC
Thank you for your bug report,
I can reproduce this bug running LibreOffice: 
Version: 4.2.0.0.alpha0+
Build ID: 164b6ce7b27c0a9ec19019e7b078b9f8f382007d
TinderBox: Win-x86@39, Branch:master, Time: 2013-09-28_16:39:4
And Mircosoft Word 2007
Comment 2 Nikhil Walvekar 2013-11-26 06:02:35 UTC
In this file, there is picture inside vml shape. That image is not preserved after save, it is stored without extension and 0 bytes.
That shape is grouped with some other shapes. For a ungrouped shape it is working properly.
Comment 3 Nikhil Walvekar 2013-12-02 07:19:23 UTC
*** Bug 65836 has been marked as a duplicate of this bug. ***
Comment 4 Mihkel Tõnnov 2013-12-02 11:32:41 UTC

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