Bug 92147 - FileCorrupt: File is getting corrupted when it was exported using UNO API
Summary: FileCorrupt: File is getting corrupted when it was exported using UNO API
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.1.0.0.alpha0+ Master
Hardware: Other All
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsDevAdvice
Depends on:
Blocks:
 
Reported: 2015-06-18 08:03 UTC by darshan.gandhi
Modified: 2019-03-21 11:25 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Diff Betwen app.xml file (176.25 KB, image/png)
2015-06-18 08:03 UTC, darshan.gandhi
Details
CorruptFile_Exported thr UNO API (7.45 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2015-06-18 08:05 UTC, darshan.gandhi
Details
Exported thr UNO API (7.54 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2015-06-18 08:05 UTC, darshan.gandhi
Details
Code to execute macro in LO using UNO API (3.82 KB, text/plain)
2015-06-22 13:44 UTC, darshan.gandhi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description darshan.gandhi 2015-06-18 08:03:06 UTC
Created attachment 116613 [details]
Diff Betwen app.xml file

Steps to Reproduce:
Comment 1 darshan.gandhi 2015-06-18 08:05:15 UTC
Created attachment 116614 [details]
CorruptFile_Exported thr UNO API
Comment 2 darshan.gandhi 2015-06-18 08:05:49 UTC Comment hidden (obsolete)
Comment 3 darshan.gandhi 2015-06-18 08:15:02 UTC
When I tried to open same corrupted file in Libre-office, its getting opened and in MS word its not.
Comment 4 darshan.gandhi 2015-06-22 12:09:45 UTC
Steps to Reproduce:

1. Record simple Macro in LO and save it.
2. Now open any MS word document in LO and execute same macro using UNO API
(Please find attached code snippet I have used to execute macro)
3. Then save back same document as MS word 2007-2013.docx format
4. and then try to open same document in MS word. 

Expected:
Document should not be corrupted
Actual:
Document is getting corrupted

Analysis on OOXML:
<AppVersion>tag is getting added in RT file (After execution of macro in LO usign UNO API) in API.xml file.
ForInstance,
 <AppVersion>5.0.0.0.alpha1$Windows_X86_64 LibreOffice_project/ddb3c4531c657cda6ae20dd950020cea1d12ba2e</AppVersion>
Comment 5 darshan.gandhi 2015-06-22 13:44:27 UTC
Created attachment 116732 [details]
Code to execute macro in LO using UNO API
Comment 6 Xisco Faulí 2018-06-12 10:44:49 UTC
Thank you for reporting the bug.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 7 QA Administrators 2019-01-11 15:21:54 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2019-03-21 11:25:58 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20190321