Created attachment 86697 [details] This bitmap has problems with PDF export PDF export: some images (see attachment) may be incorrectly exported. They look fine in the original document but are completely wrong when exported. Seems that these images are rendered as if they were encoded with something else than 24bpp (just a guess). Interestingly, MS Word 2007 reports an error in this document (corrupted file). To duplicate this bug you must select the "lossless compression" option in de PDF Options dialog.
Confirmed, I will check the ODT to be sure of the image format
Created attachment 86698 [details] Exported in PDF of the ODT in lossless compression mode
Could you please provide to us your PDF viewer, seems there is issue with evince, and not with Firefox, so perhaps this is related to the viewer, not pdf export.
Sure, good point. I use PDF-XChange Viewer. However I've just tested the PDF in Chrome and it also displays oddly.
Same behavior on your pdf software as on Acroread for android and Evince, so there is an issue with PDF export
Same problem here (with different images) Both (my images and the original attached image) are jpg's created by an adobe product (Illustrator and Adobe Photoshop CS3 Windows respectively). source: data extracted from the images with exiftool When you open one of the "adobe jpg's" with ImageMagick(display) then the colors are inverted. Perhaps this gives a clue. OS: Ubuntu 14.04/Windows XP LibreOffice 4.2.7.2 Build ID: 420m0(Build:2)
Problem still there...
** 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.0.5 or 5.1.0) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-02-21
This same bug is still present in versions 5.0.4 and 5.1.0.3. It renders incorrectly (albeit with strange differences between viewers) at least in the following PDF readers: - Adobe Acrobat Reader DC 2015.010.20059 - Google Chrome 48.0.2564.116 - Internet Explorer 11.103 - MS Edge 25.10586 - PDF-XChange Viewer 2.5 It seeems to render correctly only in: - Firefox 38 & 39
** 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Seems to have been solved in version 5.x.