New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
applying a wallpaper image does not get rid of the old one #4772
Comments
This could have been caused by #4621 Pinging @jwijenbergh as this is Wayland... |
I can confirm this on my machine as well. I posted a screencast of it on the Discord server. |
Which gpu? Also can you share the wallpaper? |
It's the integrated graphics of an AMD Ryzen 5 5500U. The wallpaper is at https://s20.directupload.net/images/240422/87h4htpr.png. It gets downscaled to 1920x1080 with the "fill" wallpaper mode of qtile. |
There is now a bug that the old background is never cleared (from qtile#4621). Let's use cairo for that (and fill the empty space with black). But, let's still do the scaling using the GPU. Hopefully fixes: qtile#4772 and also now if you apply a wallpaper but it doesn't fully contain the whole screen (mode=""), the empty space is now black instead of the old wallpaper. As far as I can tell this also was a bug before qtile#4621
Can anyone try #4785 ? |
There is now a bug that the old background is never cleared (from #4621). Let's use cairo for that (and fill the empty space with black). But, let's still do the scaling using the GPU. Hopefully fixes: #4772 and also now if you apply a wallpaper but it doesn't fully contain the whole screen (mode=""), the empty space is now black instead of the old wallpaper. As far as I can tell this also was a bug before #4621
Issue description
It seems like the new wallpaper image is added to the old one, which causes it to get iteratively brighter. For example, this is how my screen is supposed to look:
And this is how it looks like after reloading config five times:
Version
0.25.1.dev0+g005da458.d20240413
Backend
Wayland (experimental)
Config
No response
Logs
No response
Required
The text was updated successfully, but these errors were encountered: