https://bugs.documentfoundation.org/show_bug.cgi?id=134203
--- Comment #11 from Buovjaga <[email protected]> --- (In reply to Jan-Marek Glogowski from comment #10) > No. I thought it may have been fixed by > 0fedac18214a6025401c4c426466a5166553e8ec and then broken again after it and > you just unluckily skipped that in the bibisect. My assumption is that > 0fedac18214a6025401c4c426466a5166553e8ec is ok, as it's a revert. > > OTOH, while it technically reverts my commit, it also includes new code to > fix the original problem. So you can test > 0fedac18214a6025401c4c426466a5166553e8ec, but if that is still broken, you > need to rule out, that the new code introduces this, which would mean to > build LO at that commit and just revert the new part; that's a lot of work... > > Or maybe it's enough to just revert that new code part on master. In my comment 9 I should have mentioned that I checked out and tested 0fedac18214a6025401c4c426466a5166553e8ec in 7.2 repo -- You are receiving this mail because: You are the assignee for the bug.
