The attached presentation contains a single shape with a shadow and a glow effect set.
Save it as a new PPTX in Impress. (note that the glow effect is not shown, possibly unsupported?) The resulting file opens with an error in PowerPoint.
The issue seems to be that there are multiple <a:effectLst> elements after the same, they aren't grouped like in the original file. Possibly a grab-bag handling issue? (wild guess)
Observed using LO 6.0 daily build (2017-08-15_01:59:49, bebaac5eb6ebd2db3e1ea22b1630111343a9c25c) / Windows 7.
Works fine in 126.96.36.199.
Created attachment 135569 [details]
The following daily build saves the file fine, this must be a fresh regression.
Build ID: a19dc104ec008f0bb44676d63d4764c6d7442a0d
CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); Calc: group
Bug still in daily build 2017-09-04_00:07:35 (abe958a713ff0c26a3f91c558a2f227c1996c592).
Bibisected to the following commit using bibisect-linux-64-6.0. Adding Cc: to Tamás Zolnai, please take a look sometimes.
author Tamás Zolnai <email@example.com> 2017-08-14 04:11:14 (GMT)
committer Tamás Zolnai <firstname.lastname@example.org> 2017-08-14 05:37:23 (GMT)
"Decrease duplicated code"
In the bad XML the effects are listed like this:
<a:outerShdw algn="t" blurRad="76200" dir="2760000" dist="431800" rotWithShape="0">
In the good version there's no </a:effectLst> / <a:effectLst> between the two effects.
(In reply to Aron Budea from comment #5)
> Bibisected to the following commit using bibisect-linux-64-6.0. Adding Cc:
> to Tamás Zolnai, please take a look sometimes.
> author Tamás Zolnai <email@example.com> 2017-08-14 04:11:14 (GMT)
> committer Tamás Zolnai <firstname.lastname@example.org> 2017-08-14 05:37:23 (GMT)
> "Decrease duplicated code"
Yeap, it was a dump mistake. I'll revert this commit. Thanks for bisecting the commit!
Tamás Zolnai committed a patch related to this issue.
It has been pushed to "master":
tdf#111838: Revert "Decrease duplicated code"
It will be available in 6.0.0.
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.