Created attachment 109311 [details] Test image I have noticed that inserted images are looking sometimes pixelated on their borders and on analyzing this it seems some images are getting always the wrong PPI on inserting while others are getting always the correct PPI on inserting. In the attachments is an image that gets on my system always the wrong PPI. Here are the reproduction steps: 1. Start Writer and set the zoom level to 100%. 2. Go to the menu bar -> Insert -> Image -> "From File..." and choose the test image. 3. On comparing the inserted image with the original image (for example in an image viewer with a zoom level of 100%) the inserted image looks bigger. Also the borders are looking really pixelated likely due to upscaling. 4. Make a right clik on the image and go to Picture... -> Crop. 5. The image shows 72 PPI but probably it should be 96 PPI.
I see what you mean, but in Irfanview, the DPI info is 72 as well. If I open the .png in GIMP, it is totally transparent. Where did the image come from? Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information. Win 7 64-bit Version: 4.4.0.0.alpha2+ Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827 TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08
> If I open the .png in GIMP, it is totally transparent. This is probably a bug in GIMP: https://bugzilla.gnome.org/show_bug.cgi?id=740234 > Where did the image come from? It was created with GIMP and optimized with OptiPNG. But maybe the PPI isn't wrong and just another error occured but I can't say it. Also this is not the only image there I'm seeing this issue. If somebody wants to try to reproduce this: 1. Open GIMP. 2. Go to the menu bar -> File -> New..., select a width and height of 100px and click on OK. 3. Select the "Ellipse Select Tool". 4. Select the complete image with it. 5. Select the "Bucket Fill Tool". 6. Choose any color for example blue. 7. Set the opacity to 50. 8. Go to the menu bar -> File -> "Export As...". 9. Click "Export" and then again "Export". 10. Continue with the steps from the startpost.
TESTING with LO 4.4.0.1 on Ubuntu 14.04 (In reply to sworddragon2 from comment #0) > wrong PPI. Here are the reproduction steps: > > 1. Start Writer and set the zoom level to 100%. > 2. Go to the menu bar -> Insert -> Image -> "From File..." and choose the > test image (attachment 109311 [details]). > 3. On comparing the inserted image with the original image (for example in > an image viewer with a zoom level of 100%) the inserted image looks bigger. > Also the borders are looking really pixelated likely due to upscaling. CONFIRMED: jaggy edges here, and larger physically than it appears in Firefox 34.0 > 4. Make a right clik on the image and go to Picture... -> Crop. > 5. The image shows 72 PPI but probably it should be 96 PPI. CONFIRMED: PPI is 72 Status -> NEW (In reply to sworddragon2 from comment #2) > https://bugzilla.gnome.org/show_bug.cgi?id=740234 From that bug report: "This is an indexed file with an alpha channel. GIMP doesn't support this yet. If you switch the image mode to RGB, it should show up as intended." So maybe LibreOffice is having problems with an indexed file + alpha channel as well?
** 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.4 or later) 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-01-17
** 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.2.5 or 5.3.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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
*** This bug has been marked as a duplicate of bug 107703 ***