Bug 163343 - A specific ODP fails to open since 7.1
Summary: A specific ODP fails to open since 7.1
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
7.1.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: File-Opening
  Show dependency tree / graph
 
Reported: 2024-10-07 16:44 UTC by Mike Kaganski
Modified: 2024-10-10 10:35 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
A file that doesn.t open since 7.1 (1.36 MB, application/vnd.oasis.opendocument.presentation)
2024-10-07 16:44 UTC, Mike Kaganski 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Kaganski 2024-10-07 16:44:21 UTC 
Created attachment 196952 [details]
A file that doesn.t open since 7.1

The attached file opened fine in 7.0 and older. Since 7.1, it gives an error on opening.
Comment 1 Regina Henschel 2024-10-07 20:06:44 UTC 
The problem is produced by the <anim:par> element on slide "page23". If I remove it, the file opens without problem in a daily build.
Comment 2 Roman Kuznetsov 2024-10-09 11:35:01 UTC 
Confirm

Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 0a004f1a1528b8a85245de4672852b574bdc2cb2
CPU threads: 16; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: CL threaded
Comment 3 Timur 2024-10-10 10:35:19 UTC 
commit bcdcdaa5dfc5f1d50e0239055161b71e97f5f022	[log]
author	Xisco Fauli <xiscofauli@libreoffice.org>	Thu Jul 23 16:52:14 2020 
committer	Mike Kaganski <mike.kaganski@collabora.com>	Fri Jul 24 20:13:52 2020 


throw if length of keys and values are different

See https://crashreport.libreoffice.org/stats/signature/%60anonymous%20namespace'::WriteAnimateValues

This is expected to start rejecting broken files, instead of accepting invalid  data silently,
as it did before. This is not a regression, and should be indication of corrupted generator,
which is the actual cause of the bug...