I have a .sxw written ~17 years ago that loads perfectly fine in LibreOffice 6, but with LO 7.1.1.2 and 7.1.2 the text is munged together. I will attach screenshots, and will try to provide a clean document as the test case.
Created attachment 171091 [details] Screenshot of "bad" LO7 This is LO 7.1.2.2 built from FreeBSD ports on powerpc64 (big endian), FreeBSD 14-CURRENT.
Created attachment 171092 [details] Screenshot of roughly same area as the "broken" LO7 This is the screenshot of the working LO6 (6.4.7) built from FreeBSD ports on powerpc64 FreeBSD 14-CURRENT. Built with the same options as LO7, which includes: COINMP off CUPS on DOCS on GNOME off GTK3 off JAVA off KF5 off LTO off MARIADB off MMEDIA on PGSQL off QT5 on SDK off TEST off WEBDAV off I'm guessing just the QT5 setting is significant here, since it's a rendering issue.
Could you try this? export SAL_USE_VCLPLUGIN=gen && soffice then test your file.
(In reply to Julien Nabet from comment #3) > Could you try this? > export SAL_USE_VCLPLUGIN=gen && soffice > then test your file. Hi Julien, I just tried this, and still saw similar corruption. Instead of everything being a strange pale yellow, the background around the document is black, and the background of the document of the area I posted a screenshot of earlier is black.
Created attachment 171103 [details] Screenshot of same area with SAL_USE_VCLPLUGIN=gen
On FreeBSD powerpc64 LibreOffice is configured with --disable-skia, otherwise it doesn't even compile. It looks like at least a stub gets compiled, but I haven't looked at that code.
I don't know to what correspond "build from ports", for example is it the same as building from git sources directly? Anyway, the best thing would be to build from master sources (see https://wiki.documentfoundation.org/Development/BuildingOnLinux#Cloning_and_building) so you got the most up-to-date. I'd use "enable-dbgutil" option to have max details. Of course, it needs time to build and space too.
(In reply to Julien Nabet from comment #7) > I don't know to what correspond "build from ports", for example is it the > same as building from git sources directly? > Anyway, the best thing would be to build from master sources (see > https://wiki.documentfoundation.org/Development/ > BuildingOnLinux#Cloning_and_building) so you got the most up-to-date. > I'd use "enable-dbgutil" option to have max details. > Of course, it needs time to build and space too. Ports is FreeBSD's third party package build framework, that applies patches and builds packages. So it's equivalent to building from the version tarball (7.1.1.2 in this case), with applying needed patches. For LibreOffice, the ports bits can be found at https://cgit.freebsd.org/ports/tree/editors/libreoffice with the necessary patches under the files/ directory. I haven't forgotten about this, been running into problems building with dbgutil, due to requiring building all dependencies in-house, not allowing system dependencies. Packages like nss are failing, which bring down the whole thing. I'll continue trying.
A new major major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear chmeeedalf+lo, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear chmeeedalf+lo, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp