Bug 131244 - Fill a DOC form and resave as doc, MSO will complain for many errors and repairs
Summary: Fill a DOC form and resave as doc, MSO will complain for many errors and repairs
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:doc
Depends on:
Blocks: DOC-Forms
  Show dependency treegraph
 
Reported: 2020-03-09 19:31 UTC by Oliver Westphal
Modified: 2025-05-26 03:11 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
requested forms (590.27 KB, application/vnd.rar)
2020-03-10 17:25 UTC, Oliver Westphal
Details
2208e fileopen compared in MSO and LO (143.34 KB, image/png)
2020-03-11 08:57 UTC, Timur
Details
Original file downloaded from official website of a company (1.00 MB, application/msword)
2020-03-16 20:41 UTC, Oliver Westphal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Westphal 2020-03-09 19:31:45 UTC
Description:
I fill a downloaded word form and fill in the data. After saving these form as a doc-file the content and the form itself is destroyed, partly data are lost. Using word with the same form everything works well. Open and save again did it more strange.

Steps to Reproduce:
1. open the word form
2. fill in data
3.save as word file
4. reopen => data and form destroyed
5. correct everything
6. save again
7. open again => data and form muchg more destroyed

Actual Results:
see above

Expected Results:
data and form correct


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.4.1.2 (x64)
Build-ID: 4d224e95b98b138af42a64d84056446d09082932
CPU-Threads: 4; BS: Windows 10.0 Build 18362; UI-Render: Standard; VCL: win; 
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
Calc: CL
Comment 1 Timur 2020-03-10 17:10:37 UTC Comment hidden (obsolete)
Comment 2 Oliver Westphal 2020-03-10 17:25:16 UTC
Created attachment 158567 [details]
requested forms

doc form and the same form after fill in data and save it, both in .rar file format
Comment 3 QA Administrators 2020-03-11 03:25:51 UTC Comment hidden (obsolete)
Comment 4 Timur 2020-03-11 08:53:46 UTC
Please remove zipped attachement and attache separately. 
Antonia gives errors in MSO. I guess 2208 is original? You need to be precise. 
We can only use source DOC or DOCX from MSO, where were those created? 
If you already saved in LO, that cannot be used, just source.
Comment 5 Timur 2020-03-11 08:57:36 UTC
Created attachment 158591 [details]
2208e fileopen compared in MSO and LO

Also explain what exactly is "destroyed" on filesave.
Comment 6 Timur 2020-03-11 09:28:45 UTC
What I notice with 7.0+ is:
- saved DOC reopens fine in LO, but errors are detected when opens in MSO
- saved DOCX reopens with some frames wrong in LO, but better in MSO except that header image is misplaced.

DOC and DOCX are different and this bug is about DOC.
We just need to know exactly what's wrong, and wrong it is with MSO error. 
And when it started.
Comment 7 Oliver Westphal 2020-03-16 20:41:19 UTC
Created attachment 158729 [details]
Original file downloaded from official website of a company
Comment 8 Oliver Westphal 2020-03-16 20:56:50 UTC
Today I tried it again like I described in firest comment, but everything looks good and works well??? I do not aunderstand why, but no issue anymore! So sorry if it was my fault, but I have definetely no idea what was wrong first time (you can see the failures in the first file vrsion). Sorry forget the bug and close.
oliver
Comment 9 Timur 2020-03-17 09:03:59 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2022-03-19 03:32:27 UTC Comment hidden (obsolete)
Comment 11 Timur 2022-03-21 09:43:12 UTC
Repro 7.4+. While saved DOC opens in LO, errors are detected when open in MSO.
Comment 12 Timur 2022-03-24 15:47:20 UTC
Oliver, please don't mark Fixed because it's not. You may click (never email me).
Comment 13 Justin L 2023-05-26 21:18:51 UTC
repro 7.6+
Comment 14 QA Administrators 2025-05-26 03:11:46 UTC
Dear Oliver Westphal,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug