Description: Math-Formulas inserted as OLE objects into Impress are showing misaligned scalable brackets and symbols. The wrong alignment is shown only in Impress. Math itself and also Writer with embedded formulas does not show this behavior, here the formula formatting is fine. If you edit the wrong displayed formula by doubleclicking it in Impress, the Math section opens and the formula preview rendering is also as expected. Leaving the formula editor brings back the unusable formatting. Steps to Reproduce: 1. start Impress 2. insert a formula: Insert -> Object -> Formula 3. inside the math section type a formula containing fractions, surrounded by brackets or math symbols Example: A_x `=` left none A_0 over sqrt{1+ B over C } right rline _{ D rightarrow infinity } 4. close the formula editor and admire the wrong rendered formula :-) Actual Results: The placement and line width of scaled brackets / lines, root sign ets. is shifted to the right, overlaying other (right placed) formula parts Expected Results: A well rendered formula as shown in Math or Writer. Reproducible: Always User Profile Reset: Yes Additional Info: My setup: Windows 10 (x64), 24GB RAM, dual 4k-monitor Version: 7.0.3.1 (x86) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: default; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded The last version not showing this problem was Libreoffice 6.0.7. Update to higher version was neccessary after upgrading from FHD- to 4k monitor (2560x1440). Impress 6.0 was killed by another bug (presenting slides on hires monitor results in black screen with only small slide portions). The wrong formula rendering was noticed on version 6.4 and still remains on 7.0.3.1, with and without OpenGL / Skia. Did not test the versions between 6.0 and 6.4.
It seems to be a windows-specific problem. Libreoffice 6.4.6.2 on a ubuntu machine does not have this problem.
Addendum: on Windows both versions (x86 and x64) of LO 6.4 / LO 7.0 are affected.
Thanks for reporting. This issue has already been reported as bug 136891 and since been fixed, so I'm marking it as a DUPLICATE. The fix will be included in the upcoming 7.0.4 release. *** This bug has been marked as a duplicate of bug 136891 ***