Created attachment 203029 [details] Presentation exhibiting the bug Run the slideshow for the attached presentation. You'll notice that the second paragraph's number (2) appears together with the first paragraph, rather than together with the second one. The bug persists even if we remove the first paragraph's appear effect, leaving just the second paragraphs. Observed with: Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 0d986755e4153230670c820dc52cc40cd72dfa87 CPU threads: 4; OS: Linux 6.12; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US Calc: CL threaded but also with 25.2 nightlies last year.
Created attachment 203041 [details] Screenshot Runs fine for me with Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 18d4e906551a8729baaf99d34dbdc0598c9b1413 CPU threads: 16; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
Confirm with Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 8ea8e254a3151f5390f3a10ff156fcaf8e7c5d5c CPU threads: 4; OS: Linux 6.8; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded
This seems to have begun at the below commit in bibisect repository/OS linux-64-24.2. Adding Cc: to Armin Le Grand ; Could you possibly take a look at this one? It looks unrelated, but I've double checked the result. Thanks b583ccde40147bb4d49f700d114a62cb74d4773a is the first bad commit commit b583ccde40147bb4d49f700d114a62cb74d4773a Author: Jenkins Build User <tdf@pollux.tdf> Date: Fri Jun 16 20:30:29 2023 +0200 source a6e72e2b314e64f3199f3eaf1ecf78157446f6dd 152623: MCGR: tdf#155479 repair gradient SVG export for MCGR | https://gerrit.libreoffice.org/c/core/+/152623
(In reply to m_a_riosv from comment #1) So, do you think it's VCL-dependent? Also - what can we do with the (unanimated) screenshot? :-\
Created attachment 203046 [details] Animated screenshot. (In reply to Eyal Rozenberg from comment #4) > (In reply to m_a_riosv from comment #1) > > So, do you think it's VCL-dependent? > > Also - what can we do with the (unanimated) screenshot? :-\ See the number 2 in where I think is the right place.