Description: Antialiasing not great for PNG images depending on zoomlevel without OpenGL enabled.. Based on bug 86675 Steps to Reproduce: 1. Open the attached file 2. Zoom out (for me 90%) Actual Results: Letters lines appear to thin Expected Results: Same look as the jpg Reproducible: Always User Profile Reset: No Additional Info: Version: 6.3.0.0.alpha0+ Build ID: 0b21f6556b6fff76290d1095089da89532365215 CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: C
Created attachment 149159 [details] Example file
Created attachment 149160 [details] Example file
- This only shows with OpenGL disabled either on Windows, or on Linux with the "gen" vcl plugin (SAL_DISABLEGL=1 SAL_USE_VCLPLUGIN=gen). So this shouldn't be a dependency of the VCL-OpenGL bugreport. Given that we default to OpenGL on Windows and on Linux pretty much nobody uses the gen plugin, most users shouldn't be affected. - It is related to bug #80498. Presumably reverting that fixes this but reintroduces that problem. Making the image lose the alpha channel should also avoid the problem.
(In reply to Luboš Luňák from comment #3) > - This only shows with OpenGL disabled either on Windows, or on Linux with > the "gen" vcl plugin (SAL_DISABLEGL=1 SAL_USE_VCLPLUGIN=gen). So this > shouldn't be a dependency of the VCL-OpenGL bugreport. Given that we default > to OpenGL on Windows and on Linux pretty much nobody uses the gen plugin, > most users shouldn't be affected. Small note on that. The default is OpenGL. However the driver blacklist is quite long. For example: Intel OpenGL issues where fixed by blacklisting them (not quite up to date with the current situation, though). The crash reporter shows quite some report on Windows without OpenGL enabled, but could be a coincidence. Some states would be nice :-).
Dear Telesto, 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 https://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
still repro Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 78c33a4c3d1633b97049874305b3b49b820395a2 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded
Dear Telesto, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug