Created attachment 114517 [details] test case Attached there's .odb document with simple table inside that holds images as LONGVARBINARY. 1. open the form frmImages; there are 2 images on the form. First image is stored directly on the form and the other is coming form db table. 2. see the image control shows correct image on the form 3. go to menu File / Print; second image is missing on the small preview dialogue now (where you select printer) 4. print the form, second image is missing expected result: both images should be printed Note: This has been tested with MariaDB too i.e. it's not related to embedded database. Note2: it's working as expected with latest OpenOffice.
I can confirm with LO 4.4.1.2, win7
Have tested it also with early versions of LO. Bug appears also in LO 3.4 So could be it is inherited with the version of OOo LO started with. My system: OpenSUSE 13.2 64bit rpm - different LO-versions for testing.
Remarkably this actually works in 3.3 - both images show in the preview and are printed -> Keywords: regression -> Whiteboard: preBibisect
Migrating Whiteboard tags to Keywords: (preBibisect) [NinjaEdit]
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Have tested this again with Version: 5.2.4.2 Build-ID: 3d5603e1122f0f102b62521720ab13a38a4e0eb0 CPU-Threads: 4; BS-Version: Linux 4.1; UI-Render: Standard; VCL: kde4; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group (OpenSuse 42.1 64bit rpm Linux) Both images of the form were printed into a *.pdf-file. Seems the buggy behavior has gone. I will set this one to Resolved and Worksforme.