<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Application Error with invalid SAL_USE_VCLPLUGIN values" href="https://bugs.documentfoundation.org/show_bug.cgi?id=126272#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Application Error with invalid SAL_USE_VCLPLUGIN values" href="https://bugs.documentfoundation.org/show_bug.cgi?id=126272">bug 126272</a> from <a class="email" href="mailto:glogow@fbihome.de" title="Jan-Marek Glogowski <glogow@fbihome.de>"> Jan-Marek Glogowski</a> <pre>(In reply to Max A. Dednev from <a href="show_bug.cgi?id=126272#c18">comment #18</a>) > (In reply to Jan-Marek Glogowski from <a href="show_bug.cgi?id=126272#c16">comment #16</a>) > > > <a href="https://gerrit.libreoffice.org/#/c/75281/">https://gerrit.libreoffice.org/#/c/75281/</a> is now merged for 6.2.6 (merged > > 2019-07-09 22:21), which might fix the menu problem. It should be the > > equivalent of <a class="bz_bug_link bz_status_VERIFIED bz_closed" title="VERIFIED FIXED - KDE5: Calc sheet tab's context menu has unexpected highlighting" href="show_bug.cgi?id=125673">tdf#125673</a> for kde4, but I couldn't test, so it's a blind fix > > (actually I forgot a header, which was fixed by > > <a href="https://gerrit.libreoffice.org/#/c/75381/">https://gerrit.libreoffice.org/#/c/75381/</a>). > > I've tested following packages: libreoffice-6-2~2019-07-11_09.35.49_* ... > with: > SAL_USE_VCLPLUGIN=kde4 libreofficedev6.2 - works perfectly for me, no > visual issues. > SAL_USE_VCLPLUGIN=kde5 libreofficedev6.2 - starts without error messages, > 'kde5' is shown in About LibreOfficeDev window. > SAL_USE_VCLPLUGIN=qt5 libreofficedev6.2 - hangs at splash screen, > soffice.bin runs at 100% CPU usage but nothing happens. Great, so your Qt5 is >= 5.6 and the "QT_NO_VERSION_TAGGING" fix works as expected. Just make sure to always check "About LO", as LO will use a fallback, if a plugin doesn't work. SAL_USE_VCLPLUGIN is just a user preference but doesn't enforce anything. And you didn't test the most interesting use case: not using SAL_USE_VCLPLUGIN / normal startup :-) Automatically it should select "kde5" for you and "just work (TM)". Does it work for you? > According to sysprof qt5 spends most of the time somewhere in libfontconfig. The font registration for qt5 is slow, because Qt always parses the whole font. There is a reason why it's never selected automatically. You could switch it from QPainter to Cairo by using SAL_VCL_QT5_USE_CAIRO=1, which is the same the kde5 plugin does. Still even for a lot of fonts it shouldn't use more then a minute. And there is some font variant naming problem in Qt. Somehow Qt misses some fonts on startup from fontconfig and LO tries to register them. Anyway qt5 + QPainter is considered experimental playground. This needs additional work, but we had enough bugs with kde5, so work on it is postponed (there are also pending patches to run qt5 on Windows and MacOS). > > Can you try, if the current daily build is fixed regarding the menu? > > I've tried. It seems, that daily build fixes all issues with menu and other > visuals for kde4 VCL. Great :-) So except for the automatic selection test it looks like we're good for 6.2.6 with regard to these crashes. Can you test without SAL_USE_VCLPLUGIN too?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>