Created attachment 202225 [details] Screenshot of issue 1. Open Writer 2. Format - Paragraph - Area - Image Seen already in oldest of 26.2 Linux bibisect repo, so assuming it appeared in 25.8. I am unable to run most commits of 25.8 due to a crash on launch (Fedora 38 and 42 containers). The margins don't look so big with gtk3, but still grew.
That may be intentional. bibisected with linux-64-25.8 commit 7d384fb1c232f7aa720436bc68dc1de334bf7297 author László Németh <nemeth@numbertext.org> Tue Mar 25 12:21:48 2025 +0100 tdf#165984 sw cui xmloff: add Paragraph/Column/Page/Spread end zone
(In reply to Saburo from comment #1) > That may be intentional. > > bibisected with linux-64-25.8 > > commit 7d384fb1c232f7aa720436bc68dc1de334bf7297 > author László Németh <nemeth@numbertext.org> Tue Mar 25 12:21:48 2025 +0100 > > tdf#165984 sw cui xmloff: add Paragraph/Column/Page/Spread end zone That does not seem like a correct bibisect result. Did you try by doing git checkout for the bad commit, testing and then doing `git checkout HEAD~1` and testing again (should be good in the last test)?
Note that you can rediscover the binary commit hash by doing this in the bibisect repo: `git log --all --grep=7d384fb1c232f7aa720436bc68dc1de334bf7297`
Created attachment 202255 [details] screenshots(25e52f93_0b8f58a1) commit 0b8f58a18f1bcd5ab50e9556587d1e23c75abad9 Author: Jenkins Build User <tdf@maggie.tdf> Date: Tue Apr 1 18:06:31 2025 +0200 source 7d384fb1c232f7aa720436bc68dc1de334bf7297