Created attachment 191470 [details] Image not visible on page 2 If the image no longer fits on the page, it will be automatically placed on the next page. Then it becomes invisible.
If the image no longer fits on the page, it will be automatically placed on the next page. Then it becomes invisible.
Confirm Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 066b23115c2a360507e306a88da572554daefab7 CPU threads: 8; OS: Mac OS X 13.4.1; UI render: Skia/Metal; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded
Also in Version: 6.1.6.3 Build ID: 5896ab1714085361c45cf540f76f60673dd96a72 CPU threads: 4; OS: Windows 6.3; UI render: default; Locale: nl-NL (nl_NL); Calc: CL still OK in Versie: 5.2.4.2 Build ID: 3d5603e1122f0f102b62521720ab13a38a4e0eb0 CPU Threads: 4; Versie besturingssysteem:Windows 6.2; UI Render: GL; Locale: nl-NL (nl_NL); Calc: CL
Also in Version: 5.4.0.0.alpha1+ Build ID: 9feb7f7039a3b59974cbf266922177e961a52dd1 CPU threads: 4; OS: Windows 6.29; UI render: default; Locale: nl-NL (nl_NL); Calc: CL but not in Version: 5.3.1.0.0+ Build ID: aa09fd58bd499a2a2c3a32c5f613892bad54076c CPU Threads: 4; OS Version: Windows 6.29; UI Render: default; Layout Engine: new; Locale: nl-NL (nl_NL); Calc: CL
This seems to have begun at the below commit in bibisect repository/OS bibisect-linux-64-5.4. Adding Cc: to Miklos Vajna ; Could you possibly take a look at this one? Thanks 57765e5199df63e3def923f259bf5e6352d575c5 is the first bad commit commit 57765e5199df63e3def923f259bf5e6352d575c5 Author: Jenkins Build User <tdf@pollux.tdf> Date: Wed Feb 8 08:29:33 2017 +0100 source 689cead9e0837dc932e3a4cd765f7d319b529018 141167: tdf#151060 sw PDF export: don't paint off-page part of drawing object | https://gerrit.libreoffice.org/c/core/+/141167
raal: I'm a bit confused, your bisect result points to 689cead9e0837dc932e3a4cd765f7d319b529018, a commit from 2016. My later commit is bab44a97d21d0ac8a8a06678e71024c1a830943f, from 2022. Did you mean to ping Michael S instead? Thanks.
(In reply to Miklos Vajna from comment #6) > raal: I'm a bit confused, your bisect result points to > 689cead9e0837dc932e3a4cd765f7d319b529018, a commit from 2016. My later > commit is bab44a97d21d0ac8a8a06678e71024c1a830943f, from 2022. > > Did you mean to ping Michael S instead? Thanks. Hi Miklos, yes, sorry, my mistake. Michael, please can you take a look?
*** This bug has been marked as a duplicate of bug 154128 ***