Description of problem: I have used Libreoffice 6.3 on Mageia 7 on a desktop PC because I needed the Firebird engine. I created forms in which I placed an image on the page and reports where I put the same image on the page header. I copied the odb to a Win10 laptop where the LibreOffice got upgraded to 6.4.4 without problems. All display the same way as on the 6.3 dessktop. I did the LibreOffice update from Mageia's repo to 6.4.4 on the laptop (has both Mageia and Win10 partitions, no sharing of partitions) and there the dimensions of the image on both forms and reports are not respected, they turn out too large (about the size of the original png file). On the desktop I removed the Libreoffice 6.3 and installed the rpm's from the LibreOffice site and there the issue with the images does not occur. Version-Release number of selected component (if applicable): LibreOffice 6.3.2 - 6.4.4 How reproducible: Steps to Reproduce: 1. 2. 3.
Thank you for reporting this, Herman. and the experiment: > I removed the Libreoffice 6.3 and installed the rpm's from the LibreOffice > site and there the issue with the images does not occur Assigning to neoclust who did the most recent M7 LibreOffice version updates.
Source RPM: (none) => libreoffice-6.4.4.2-1.mga7.src.rpmAssignee: bugsquad => mageia
is it still valid with libreoffice 6.4.7.2?
Yes. I run the forms as stanadalone, and there in its .odt file I can reduce the image size. But reports are generated each time afresh in the .odb an there it is always way too big (almost page size) when running the report. It looks OK in Design View.
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Since then LO has moved to veersion 7.0.4.2 and the problem does not occur there anymore. Closing.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED