<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Do not default to KDE5 VCL plugins under LXQt" href="https://bugs.documentfoundation.org/show_bug.cgi?id=123595#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Do not default to KDE5 VCL plugins under LXQt" href="https://bugs.documentfoundation.org/show_bug.cgi?id=123595">bug 123595</a> from <a class="email" href="mailto:yen@chyen.cc" title="Chih-Hsuan Yen <yen@chyen.cc>"> Chih-Hsuan Yen</a> <pre>> if you have any good idea on how to properly address this in LibreOffice, I'll be happy about that one. Not trying KDE/Qt plugins at all appears to be the simplest solution. No more worries about extra environment variables and additional packages. That is, use pStandardFallbackList instead of pKDEFallbackList for DESKTOP_LXQT in vcl/source/app/salplug.cxx. > Otherwise it seems to me like the only way to deal with it for now is that it's up to the users/admins to install the required packages if they want to use kde5. > Does that make sense? If a VCL plugin requires extra packages to work, it's better to not make it as the default IMO. Users who want it can just specify SAL_USE_VCLPLUGIN. > Maybe, the qt5 VCL plugin might be an alternative when the "SAL_VCL_QT5_USE_CAIRO=true" environment variable is set in addition, but I can't really tell how well this works (i.e. setting "SAL_VCL_QT5_USE_CAIRO=true" and "SAL_USE_VCLPLUGIN=qt5" via the distro). That's also an option. We (LXQt developers) can add default environment variables in lxqt-session. In a previous comment you said the qt5 VCL plugin is not recommended for daily use. Is the combination SAL_VCL_QT5_USE_CAIRO=true SAL_USE_VCLPLUGIN=qt5 considered stable enough for daily use?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>