Created attachment 119277 [details] sample Steps: 1) Open attached document 2) Notice that the bitmap pattern is blurry at 100 percent and when zoomed in Regression as this doesnt happen with in 3.3.0 and 3.5.7. Version: 5.1.0.0.alpha1+ Build ID: 329496c1f75f97d2e6119ceb214a2ea1fbadb17a TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2015-10-03_02:47:24 Locale: en-US (en_US.UTF-8)
Created attachment 119278 [details] screenshot
Confirmed. Win 7 Pro 64-bit, Version: 5.0.2.2 (x64) Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe Locale: fi-FI (fi_FI)
Migrating Whiteboard tags to Keywords: (bibisectRequest) [NinjaEdit]
I think there's a reasonable argument that this should be set to normal - high (regression). Normal because there is no real workaround so it could prevent high quality work - the image is blurry. 8aabf2aee6514311020b855a95a6e44bab3a5b0d is the first bad commit commit 8aabf2aee6514311020b855a95a6e44bab3a5b0d Author: Bjoern Michaelsen <bjoern.michaelsen@canonical.com> Date: Wed Nov 27 09:32:23 2013 +0000 source-hash-0aa9ced531b8d85ad067c1d156a9708eea628d78 commit 0aa9ced531b8d85ad067c1d156a9708eea628d78 Author: Tor Lillqvist <tml@collabora.com> AuthorDate: Wed Nov 6 00:43:06 2013 +0200 Commit: Tor Lillqvist <tml@collabora.com> CommitDate: Wed Nov 6 00:44:28 2013 +0200 It's types.rdb now, not udkapi.rdb any more Change-Id: If6e8c4862ec628eb4c052e0fd237f5aef89db8eb :100644 100644 ce5cd8dc3c3a6fdc22ae8e4f63897ab07254eddb 867d2798c91ad285850e29c0e8d0f40548dff4fb M ccache.log :100644 100644 405359894d6958b64eb7f2beb6f8a48550779f95 e461af99260d551289a2dd1f188119438cf1fc19 M commitmsg :100644 100644 0c7b842ac949f66eaa350d1ac25b0d6ccc407841 ab6adaea7a96b5d6d10dda3f10504fd1f005cfcf M make.log :040000 040000 216184b3333359e5a1395b47d1551dd3b61d2f04 d765efa8f9bd443222a2a557954f9dd4997fd3e7 M opt # bad: [423a84c4f7068853974887d98442bc2a2d0cc91b] source-hash-c15927f20d4727c3b8de68497b6949e72f9e6e9e # good: [65fd30f5cb4cdd37995a33420ed8273c0a29bf00] source-hash-d6cde02dbce8c28c6af836e2dc1120f8a6ef9932 git bisect start 'latest' 'oldest' # skip: [e02439a3d6297a1f5334fa558ddec5ef4212c574] source-hash-6b8393474974d2af7a2cb3c47b3d5c081b550bdb git bisect skip e02439a3d6297a1f5334fa558ddec5ef4212c574 # skip: [d1cca78ab77d64482b6643bc643d29dbe2dd1442] source-hash-2d19e9bb07ccff3134f855812dddfda5c07b1fe4 git bisect skip d1cca78ab77d64482b6643bc643d29dbe2dd1442 # skip: [d1cca78ab77d64482b6643bc643d29dbe2dd1442] source-hash-2d19e9bb07ccff3134f855812dddfda5c07b1fe4 git bisect skip d1cca78ab77d64482b6643bc643d29dbe2dd1442 # good: [585e04fc6e242295b8a821029acae377dcab7340] source-hash-ae5c574ac24ed8979dcf03da87cd14c078db2a07 git bisect good 585e04fc6e242295b8a821029acae377dcab7340 # good: [585e04fc6e242295b8a821029acae377dcab7340] source-hash-ae5c574ac24ed8979dcf03da87cd14c078db2a07 git bisect good 585e04fc6e242295b8a821029acae377dcab7340 # bad: [a14f5a99eeeef6a730d9726f17ab53fbbe04da5b] source-hash-65d9783d8bc2ffec5bf6fd989c9bc0d709194e5f git bisect bad a14f5a99eeeef6a730d9726f17ab53fbbe04da5b # bad: [a14f5a99eeeef6a730d9726f17ab53fbbe04da5b] source-hash-65d9783d8bc2ffec5bf6fd989c9bc0d709194e5f git bisect bad a14f5a99eeeef6a730d9726f17ab53fbbe04da5b # good: [3b187f1cb396a02f99a3da44b8b1daa40d795749] source-hash-344d80ee1d3829b28c18135ac4f0500d4b69aedd git bisect good 3b187f1cb396a02f99a3da44b8b1daa40d795749 # good: [e014985ca41d06649533c7bedb4f029cbcb4ed6e] source-hash-af40ffdcef60c65437df4749c8bb2ad24356d1c2 git bisect good e014985ca41d06649533c7bedb4f029cbcb4ed6e # skip: [9fc19519e5bc25b68aff579d6f6dd57553e21cb4] source-hash-d63a69a087c9c7641e28e2002d7ad56076d08ca1 git bisect skip 9fc19519e5bc25b68aff579d6f6dd57553e21cb4 # skip: [8cb23b3181bfae3988e27d5621476e8fc74ab823] source-hash-132731f0704b5a9e996cb0d413c8e369efe8875f git bisect skip 8cb23b3181bfae3988e27d5621476e8fc74ab823 # good: [4360256bc0b1443028a057164fbbdb43847ce68d] source-hash-40543e5321c8f618c125fd6f7f9a24b87431277a git bisect good 4360256bc0b1443028a057164fbbdb43847ce68d # good: [4360256bc0b1443028a057164fbbdb43847ce68d] source-hash-40543e5321c8f618c125fd6f7f9a24b87431277a git bisect good 4360256bc0b1443028a057164fbbdb43847ce68d # bad: [8aabf2aee6514311020b855a95a6e44bab3a5b0d] source-hash-0aa9ced531b8d85ad067c1d156a9708eea628d78 git bisect bad 8aabf2aee6514311020b855a95a6e44bab3a5b0d # bad: [8aabf2aee6514311020b855a95a6e44bab3a5b0d] source-hash-0aa9ced531b8d85ad067c1d156a9708eea628d78 git bisect bad 8aabf2aee6514311020b855a95a6e44bab3a5b0d # good: [e1c300f1d24977d8ea10e57115516174929bbc23] source-hash-832586588c3ed5f1686a4ecebc2ed198ce049b24 git bisect good e1c300f1d24977d8ea10e57115516174929bbc23 # good: [e1c300f1d24977d8ea10e57115516174929bbc23] source-hash-832586588c3ed5f1686a4ecebc2ed198ce049b24 git bisect good e1c300f1d24977d8ea10e57115516174929bbc23 # good: [11ac44b0fb233f1f98e2f083598f6720a04e457f] source-hash-3c01203ea657b9a3538f9956591b3d4da5fce6e7 git bisect good 11ac44b0fb233f1f98e2f083598f6720a04e457f # first bad commit: [8aabf2aee6514311020b855a95a6e44bab3a5b0d] source-hash-0aa9ced531b8d85ad067c1d156a9708eea628d78
Ok, adjusting prio+sev.
** 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
Regression introduced in range https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=3c01203ea657b9a3538f9956591b3d4da5fce6e7..0aa9ced531b8d85ad067c1d156a9708eea628d78
Probably look at https://cgit.freedesktop.org/libreoffice/core/commit/?id=36f21914b31a28f75ec2195c266424a18408f747
** 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
Hi I think the reason why this happen is that the pattern's are defined for 96 dpi and were scaled to something else within LibO shapes. There are some options - pattern use png files which will be zoomed (that's the resolution now and make blured shape patterns) - we can use svg files for pattern instead of png (is now not possible) - make the pattern png file size fit 300 dpi instead of 96 dpi any idea how to solve this?
Would either resolve the ticket as WF (see comment 4) or go with vector graphics (see comment 10). What's your opinion, Tomaz?
Dear Yousuf Philips (jay) (retired), 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
(In reply to Heiko Tietze from comment #11) > Would either resolve the ticket as WF (see comment 4) or go with vector > graphics (see comment 10). What's your opinion, Tomaz? Creating a SVG for the pattern, where instead of pixels we would have rectangles is an interesting idea.