Created attachment 149772 [details] Before & after SUMMARY *** After upgrading to Plasma 5.25, the icons on the Latte became blurry (file attached). *** STEPS TO REPRODUCE 1. Upgrade to Plasma 5.25 Need to understand what caused it. Latte config not changed. Any size 16/22/32/48/64 and etc have blur and not perfect pixel align now after upgrade to Plasma 5.25. Latte-dock: 0.10.8 Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.17.0-9.1-liquorix-amd64 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i5-10400F CPU @ 2.90GHz Memory: 7.7 ГиБ of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 Manufacturer: ASUS
no idea, the fact that you are using NVidia might be related. Latte is using Kirigami.Icon for its icons I wouldnt be surprised if something in Kirigami updates broke the icons implementation in general.
Nvidia... hm, but previous Plasma/Kirigami version rendered fine. Maybe anybody test it on open source GPU's (Intel or AMD). I'm inclined too that the problem is caused by Kirigami. I also tried to change the size by 49 pixels in the Latte configuration, but this is not applicable, since I realized only even values are possible. By opening the screenshot in Gimp and zooming in, you may notice that the icon stretches by 1 pixel horizontally, but not vertically.
Created attachment 149775 [details] Horizontal stretch
Hmm, and if you place the dock on the left or right, then the opposite effect occurs. Icons stretch vertically, but not horizontally.
sorry but I can not maintain/follow v0.10.x versions any more... There will be one more 0.10.9 version in order to provide some basic functionality for plasma 5.25 but all focus is now at git version that will be in one month time the next stable v0.11.x . Please try Latte git version to confirm that this is still valid for v0.11.x or wait for v0.11.x to be released to check out things...
I tested it with Latte git version that will be upcoming v0.11 and it works just fine... after v0.11 is released this bug will be closed.