Bug 164708 - FILESAVE: ODP with grouped shape fails to open in PP when saved to PPTX
Summary: FILESAVE: ODP with grouped shape fails to open in PP when saved to PPTX
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
Version:
(earliest affected)
7.3.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: PPTX-Corrupted
  Show dependency treegraph
 
Reported: 2025-01-14 14:06 UTC by Aron Budea
Modified: 2025-02-09 12:00 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Sample ODP (14.86 KB, application/vnd.oasis.opendocument.presentation)
2025-01-14 14:06 UTC, Aron Budea
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aron Budea 2025-01-14 14:06:27 UTC
Created attachment 198537 [details]
Sample ODP

Open the attached sample ODP, which contains a group shape taken from attachment 67683 [details] (from bug 30583), save it to PPTX, and try opening the PPTX in PowerPoint.

=> PowerPoint encounters a problem, and tries to repair the file.

Observed in 25.8.0.0.alpha0+ (72df5a6fdf3e14d9994ebd1de269ab712136a27a) / Windows.

This is a regression from the following commit, bibisected using repo bibisect-win64-7.3:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=4bfe8304a5600e236043e4ad7c6dc75fd05c937b
author		Tibor Nagy <nagy.tibor2@nisz.hu>	2021-10-18 14:51:05 +0200
committer	László Németh <nemeth@numbertext.org>	2021-11-03 15:01:31 +0100

tdf#144914 PPTX export: fix interactions and hyperlinks on shapes
Comment 1 m_a_riosv 2025-01-15 15:55:36 UTC
Reproducible
Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: e146f49704ef535c9ddd74338783e7c38390bf59
CPU threads: 16; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win
Locale: en-US (es_ES); UI: en-US
Calc: CL threaded
Comment 2 Aron Budea 2025-02-07 17:41:39 UTC
This bug actually got resolved a while ago. The exported file is still corrupted, but because of a different issue, introduced after this, and before the other got fixed, so at first it seemed like it's all because of a single bug.

I'm closing this as WFM, and going to open a new bug report for the other regression with a slightly modified sample.
Comment 3 Aron Budea 2025-02-09 12:00:35 UTC
Bug 164775 is the follow-up, I've added the modified sample there.