https://bugs.documentfoundation.org/show_bug.cgi?id=165135

            Bug ID: 165135
           Summary: FILESAVE PPTX Assertion failure when saving attached
                    PPT as PPTX
           Product: LibreOffice
           Version: 25.8.0.0 alpha0+
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: filters and storage
          Assignee: [email protected]
          Reporter: [email protected]
            Blocks: 105537, 108226

Created attachment 199080
  --> https://bugs.documentfoundation.org/attachment.cgi?id=199080&action=edit
PPT sample

This is an assertion failure, and only occurs in builds where those are
enabled, typically debug builds.

Open attached PPT in LO, and save it as PPTX.

-> You get:
Assertion failed: iter != maPlaceholderShapeToIndexMap.end(), file
D:/sources/libreoffice/sd/source/filter/eppt/pptx-epptooxml.cxx, line 2484

Observed using a debug build of 25.8.0.0.alpha0+
(6042e60d69c40d1f307710e60a278cb286d68603) / Windows.

The assert is in the following line:
https://opengrok.libreoffice.org/xref/core/sd/source/filter/eppt/pptx-epptooxml.cxx?r=76c6d180f398a7d482665c24c07ec75f8a1dc7cd#2484

And was added in the following commit on 2023-12-04:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=cdb180e767ebf2011414f4a5ba7213752474ee36

I don't know if it's related, but in a daily build (non-debug), when saving the
PPTX to PPT, the result is occasionally corrupted, PowerPoint can't open it.
Interestingly, I've only encountered that with manual open/save, if I do
--convert-to, the result could always be opened in PowerPoint. It might be
worth checking separately, but only after this assertion failure is gone.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=105537
[Bug 105537] [META] Assertion failed crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=108226
[Bug 108226] [META] PPTX (OOXML) bug tracker
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to