Open the document tdf118701.docx. That document belongs to test testTdf118701 in ooxmlexport15.cxx https://opengrok.libreoffice.org/xref/core/sw/qa/extras/ooxmlexport/data/tdf118701.docx Open it in Word. You will see a huge X on page 2 and a huge X on page 4. Open it in a daily build. The X characters are missing or at wrong place. I came across the problem, because the wrongly placed X force the document to 8 pages and so makes the unit test fail. Sometimes you get 4 pages, but then the X are missing. I see the problem in Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 4e2ce2a460458f17ee4360c45a2da2fc4b4d753e CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL and in Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: d05c176cc022f1b771f7c064f6ce74e9f8c27a1b CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
Regression since commit 6ebf46e332facfae5fd6027ec667ccd5993dd493 Author Caolán McNamara <caolanm@redhat.com> Date Wed May 04 12:38:14 2022 +0100 upgrade to latest harfbuzz Seems to be Windows-only. Sometimes the problem takes several open/close attempts to appear.
I had no luck reproducing this with local master builds on either macOS or Windows. I opened the files several times without closing LO and I always get 4 pages with fully visible large X glyphs on page 2 and 4.
With master built today, and profile reset, I also can't repro: Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 262df14af32be6855b276dcf7548d3b233076ec6 CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL threaded
Yes, seems to be fixed. A local build from Friday has the error, but a local build from Sunday is OK. So let us set it to worksforme.
It would be interesting to know which commit fixed it, because it is such a strange bug to happen after a HarfBuzz upgrade.
(In reply to خالد حسني from comment #5) > It would be interesting to know which commit fixed it, because it is such a > strange bug to happen after a HarfBuzz upgrade. I will try (to remember) to bibisect it, when 7.5 bibisect repo gets updated to today's commits.