https://bugs.documentfoundation.org/show_bug.cgi?id=149728
--- Comment #11 from Michael Weghorn <[email protected]> --- (In reply to Max from comment #9) > IMO, the issue is not a case of appimg script. > > It also affects on self compiled binaries such in Gentoo, not only AppImg > created from debs. > > Is affects Manjaro too. > > (...) > > But I've tested Master Daily rpm in OpenSuse tumbleweed VM - it works fine. OK, let's leave this bug open for now then. It surprises me that it works with the same version for the non-AppImg case, but not if it's an AppImg, since my (maybe naive) expectation would be that it should just behave the same way, given the same files from the LO build are used. But then, I don't know much about AppImg. Is any sandboxing,... involved there? (I know that is the case for Flatpak and Snap, but thought that it isn't for AppImg in general.) Some typical "suspects" that come to my mind that may usually play a role when things behave differently on different systems for the kf5 VCL plugin: * Qt library versions * KF5 library /Plasma version * other system libs * X11 vs Wayland * user profile/settings (for either LO or KDE Plasma) This *might* be relevant for different behavior across distros, but I don't see how it would explain the AppImg vs. non-AppImg difference, unless the generated AppImg file includes different libraries than the system ones. (I don't know much about AppImg, though.) Without any clear steps to reliably reproduce this in a development setup, I fear it's unlikely that this will get fixed soon. If you can identify what's the relevant part that makes it work on one system, but not another, that might be of much help. What you could also try is to identify from which commit on this no longer works, by doing a bibisect using the 7.3 bibisect repo (in case the problem is reproducible with this repo). More details here: https://wiki.documentfoundation.org/QA/Bibisect > Created attachment 181082 [details] > Console output of Master Daily AppImg > > (...) > As I wrote above during appimg runtime there was a lot warnings about vcl > (see an attachment). Those shouldn't be related to the issue discussed here. The java warning should go away if you install a JRE (and maybe have to select it in the LO settings). -- You are receiving this mail because: You are the assignee for the bug.
