<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Assertion failure when checking font preview for certain fonts in LOOL" href="https://bugs.documentfoundation.org/show_bug.cgi?id=132445#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Assertion failure when checking font preview for certain fonts in LOOL" href="https://bugs.documentfoundation.org/show_bug.cgi?id=132445">bug 132445</a> from <a class="email" href="mailto:baron@caesar.elte.hu" title="Aron Budea <baron@caesar.elte.hu>"> Aron Budea</a> <pre>(In reply to Jan-Marek Glogowski from <a href="show_bug.cgi?id=132445#c1">comment #1</a>) > I think the "fix" for <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Assertion failure when opening a document in LOOL (w certain fonts installed)" href="show_bug.cgi?id=132424">bug 132424</a> may simply paper over the real problem. If > the same happens for loading documents without that fix, that somehow means > font handling isn't working correctly at this point. Guess someone needs to > look into the original weld patch and see what is different now. Right, what Caolán wrote there is that the assert is actually unrelated to the weld patch, it just became triggered at a different time. I could verify that right before the weld patch it could be triggered with the same repro steps as in the description above, thus the patch identified in <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Assertion failure when opening a document in LOOL (w certain fonts installed)" href="show_bug.cgi?id=132424">bug 132424</a> is irrelevant when it comes to the assert.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>