Bug 147460 - Writer Master Document modify value of data field after an exportation to PDF
Summary: Writer Master Document modify value of data field after an exportation to PDF
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Writer-Master-Doc
  Show dependency treegraph
 
Reported: 2022-02-16 12:35 UTC by titanemdg
Modified: 2024-02-17 03:13 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
These files are a test which shows he error (49.36 KB, application/x-zip-compressed)
2022-02-16 12:43 UTC, titanemdg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description titanemdg 2022-02-16 12:35:09 UTC
Description:
Writer modify value of a fields of data coming from external source. This occurs in a Master Document. The inserted Writer document contains a link to another Spreadsheet. After exporting the M.D to pdf, values of some fields are modified on both source and destination.

Steps to Reproduce:
1.create a Writer document
2.Insert data from a spreadsheet to the document. Link it as DDE.
3.Make above 1 and 2 twice to obtain 4 files: 2 writer and 2 sheet
3.Insert the 2 Writers document in a Master document. At this stage all fields are right.
4. Export the master document to PDF
5. Some fields in PDF are wrong and Writer set the same wrong data in the master document.

Actual Results:
Wrong data for some fields

Expected Results:
Do not modify data


Reproducible: Sometimes


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Master document do no have to change any value of any fields after exportation.
Comment 1 titanemdg 2022-02-16 12:43:48 UTC
Created attachment 178306 [details]
These files are a test which shows he error

Please change the path in the Navigator for both page1.odt and page2.odt
Comment 2 Buovjaga 2022-02-16 13:02:01 UTC
I reproduce the change on page 3

Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 583185235389b55d6cfffac3067c0e1ccb2852b1
CPU threads: 2; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: fi-FI (fi_FI); UI: en-US
Calc: threaded Jumbo
Comment 3 Buovjaga 2022-02-16 15:25:14 UTC
Already in oldest of Linux 6.3 bibisect repo
Comment 4 Buovjaga 2022-02-16 15:43:19 UTC
Already seen in 3.5.0 and 3.3.0.
Comment 5 QA Administrators 2024-02-17 03:13:10 UTC
Dear titanemdg,

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