Bug 171537 - FILEOPEN DOCX: chart is not visible anymore (until it is ungroupped)
Summary: FILEOPEN DOCX: chart is not visible anymore (until it is ungroupped)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
24.8.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bisected, regression
Depends on:
Blocks: Chart
  Show dependency treegraph
 
Reported: 2026-03-28 14:11 UTC by Justin L
Modified: 2026-03-28 15:33 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
forum-mso-en-14364.docx: example document (complex - groupshaped chart not visible now) (56.06 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2026-03-28 14:11 UTC, Justin L
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Justin L 2026-03-28 14:11:16 UTC
Created attachment 206443 [details]
forum-mso-en-14364.docx: example document (complex - groupshaped chart not visible now)

Starting with LO 24.8.4, the chart in this document is no longer visible (until ungroupped from the visible textbox).

While technically this is a 24.8.4 regression from 
commit acf704eca7e14a2faea1d3b6e66718db07f8b041
Author: Mike Kaganski on Tue Nov 26 10:40:10 2024 +0100
   tdf#146269: don't set modified when connecting frame, model and controller
   Reviewed-on: https://gerrit.libreoffice.org/c/core/+/177300
it seems to have just exposed some weakness elsewhere.

Given the fact that this is the only document noticed so far that was negatively affected by that commit (and no other reports found bisected to this commit) I'm not marking this as a blame.

However, a revert of the commit still 'fixes' the problem.

Steps to reproduce:
1.) open forum-mso-en-14364.docx in LO

There should be a graph visible in the bottom half of the page.

Found by Collabora's mso-test
Comment 1 Justin L 2026-03-28 15:33:33 UTC
From what I can see during debugging, a lot of things get "notified" when something is set as modified. So there must be some kind of registration not happening when this notification is blocked.

For the low importance of the bug this patch was fixing, perhaps simply reverting it might be the safest thing. It doesn't sound like a convincing change to keep.