Bug 146532 - Linking objects from Calc to Write in DDE mode.
Summary: Linking objects from Calc to Write in DDE mode.
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2022-01-02 22:19 UTC by gmarco
Modified: 2022-01-05 03:41 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:
Regression By:


Note You need to log in before you can comment on or make changes to this bug.
Description gmarco 2022-01-02 22:19:04 UTC
Now, with L.O., the connection works correctly again.
There remains a minor bug that I had already reported in the past.
When opening a text document that has links to scalc files embedded, you are asked if you want to update it or not (in the meantime the data in the spreadsheet may have changed).
Choosing "YES" the embedded object will reflect the current state of the data in the spreadsheet.

At this point, closing the ODT file, the bug can occur if the closing is performed by clicking on "X" as commonly used.

a) if the document has not been further edited (changes to the actual text), the closure takes place without saving (and this without even a warning) losing the upgrades.

b) the problem does not occur in all other cases:
- the text has also been changed
- the embedded ODS data has been updated manually from "Edit> Links to external files ..." (Update button)
- close the ODT file with "Save" or "Save with name".

Question: is this a bug? or is the fact intentional? in the latter case, I think it would be right to indicate it and prevent possible damage with a warning.
Comment 1 m.a.riosv 2022-01-03 22:56:09 UTC
If it is already reported, add in that one, that bug still remains, adding the information about the last version tested. Se we can close this one as dupliclate.
Comment 2 gmarco 2022-01-04 08:35:42 UTC
Referring to the "X" question, where is it reported?
If you intend my original bug 91817, that is dated 2015-06-02 but the problem is already here.
Comment 3 QA Administrators 2022-01-05 03:40:58 UTC Comment hidden (obsolete)