Created attachment 125531 [details] bugged-panel SUMMARY STEPS TO REPRODUCE 1. Update to latest latte-dock-git 2. Start a session with latte 3. Have a wallpaper that triggers background (Smart Colors with designated wallpaper switcher for better color detection). OBSERVED RESULT Panel's background have two distinctive layers, a stronger and lighter one. See attached photos. EXPECTED RESULT Background should be consistent. Operating System: Manjaro Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 Kernel Version: 5.5.0-1-MANJARO OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 7,6 GiB ADDITIONAL INFORMATION Opening options, changing unrelated settings and changing them back to previous state fixes the bug for given session. After restart, big shows up again. I'll give more info but I'm not sure what is relevant.
Send me please your Latte layout file and a link for that specific wallpaper from the screenshot.
When I opened Layout Manager, it showed up some warning that the current Layout is corrupted and I need to delete it but... I can't since the Delete button is grayed out. I can delete all other layouts thou... I'm sending the file and the screenshots, but I wonder if it contains some private info? I modified the layout file that I sent here: calendar_id_list and refresh_token, since everyone can download it. The wallpaper doesn't matter. The bug ALWAYS shows up when background is present. With wallpapers where smart function makes it fully transparent, the issue is invisible. In other cases it's still present. So it's enough to switch from wallpaper to wallpaper and see which one triggers the background. If there is one, then the bug is visible.
Created attachment 125550 [details] layout file
Created attachment 125551 [details] warning message
Created attachment 125552 [details] grayed out option to delete the layout I realized now, that the Delete option is grayed out when the layout is chosen and active. So I have to switch it to something else, but I don't want it, because creating new layout is a tedious task and current one is good, aside this issue.
Uh, I wanted to modify the layout file and had already done that but forgot to save it, so I attached the unmodified version. I can't see any option to delete the file. Or maybe those data is OK? If this is a sensitive data, please, ask someone who has ability to remove the attachment and I'll upload the fixed version.
I have sent https://phabricator.kde.org/T12617 for the layout sensitive data
BTW if you disable BLUR option for top panel this is fixed right? Probably for some reason the BLUR AREA sent to KWIN is faulty
The content of attachment 125550 [details] has been deleted for the following reason: Per user request. (TA)
Git commit 8ab5779bcbc5c6f4604afb11efeeca56faa77641 by Michail Vourlakos. Committed on 30/01/2020 at 20:02. Pushed by mvourlakos into branch 'master'. compute blur area correctly on startup --improve calculations for Effects area during startup and at the same time when the dock is totally hidden so it should not paint any effects area at all. FIXED-IN:0.9.9 M +12 -17 app/view/effects.cpp M +22 -9 containment/package/contents/ui/PanelBox.qml https://commits.kde.org/latte-dock/8ab5779bcbc5c6f4604afb11efeeca56faa77641
Git commit b11dacc0042b0ba902bcb92c4ce16562ad63aae2 by Michail Vourlakos. Committed on 30/01/2020 at 20:04. Pushed by mvourlakos into branch 'v0.9'. compute blur area correctly on startup --improve calculations for Effects area during startup and at the same time when the dock is totally hidden so it should not paint any effects area at all. FIXED-IN:0.9.9 M +12 -17 app/view/effects.cpp M +22 -9 containment/package/contents/ui/PanelBox.qml https://commits.kde.org/latte-dock/b11dacc0042b0ba902bcb92c4ce16562ad63aae2
I discovered that bug didn't always show, so there are times when it's pretty consistent and other times it's gone, but then it shows up again. I haven't updated git yet to observe it for a while, but when I finally do update it, I also let myself to watch it for a longer time and then report it back if it solved the issue.
I applied the fixed version. Two weeks have passed and the issue is gone for good, so it's safe to say that this really fixed. Thank you :)