Bug 79536 - FILEOPEN: File with charts corrupted and cannot be opened in MS-WORD
Summary: FILEOPEN: File with charts corrupted and cannot be opened in MS-WORD
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.4.0.0.alpha0+ Master
Hardware: Other All
: medium normal
Assignee: Yogesh Bharate
URL:
Whiteboard: BSA target:4.4.0
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-02 10:26 UTC by Yogesh Bharate
Modified: 2014-06-05 07:50 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
document contains charts (76.42 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2014-06-02 10:26 UTC, Yogesh Bharate
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yogesh Bharate 2014-06-02 10:26:28 UTC
Created attachment 100281 [details]
document contains charts

Problem description: 

Steps to reproduce:
1. Open document in LibreOffice.
2. save as .docx
3. Open in MS Office 2010.

Current behavior:
Document get corrupted.

Expected behavior:
Document should open in MS Office 2010.
              
Operating System: All
Version: 4.4.0.0.alpha0+ Master
Comment 1 Yogesh Bharate 2014-06-02 10:31:25 UTC
Note :
1. After RT, When we close LibreOffice tab, its asked for saving document contains.
2. If we click on save, RT get corrupted when we open in MS Office 2010.
3. If we click on close without saving, RT document get open in MS Office 2010.
Comment 2 Jorendc 2014-06-03 20:29:53 UTC
Repro :-)

Version: 4.4.0.0.alpha0+
Build ID: b447687292334687a371b66d7ad56ba9662b898e
TinderBox: Win-x86@39, Branch:master, Time: 2014-06-03_06:24:04
Comment 3 Yogesh Bharate 2014-06-05 07:01:32 UTC
- Check the issue attached document on
  Version: 4.4.0.0.alpha0+
  Build ID: 10ec4a7cb24da8ced86880bbceeca4d2ad3436f1 build.
- After Miklos e2b260fc98e833d4e64426b90992094f2da0498c patch issue get fixed.
Comment 4 Jorendc 2014-06-05 07:50:13 UTC
Thanks for updating this bug Yogesh! Really appreciated.

Kind regards,
Joren