GNOME Bugzilla – Bug 789624
Current wallpaper no more previewed in control-center with gtk 3.22.25 under X
Last modified: 2017-11-01 15:05:04 UTC
Created attachment 362494 [details] g-c-c. background setting - ArchLinux 64 bit - gtk3-3.22.25 - xorg-server 1.19.5-1 - xf86-video-nouveau 1.0.15-2 - gnome control center 3.26.1 ... after recent update of gtk3 libs from v3.22.24 to 3.22.25, the current wallpaper preview in the gnome control center / backgroung setting page is no more displayed: instead of the current wallpaper preview, you can see only the preview of gnome-shell top panel The lock screen image preview is displayed without any issue I've attached an evidence of the issue... fyi , downgrading gtk3 lib to ver. 3.22.24 solve the issue Obvioulsy feel free to reassing bug to the correct team if this one is not related to gtk3 libs Regards Andrea
just updated to gtk 3.22.25 on my Arch. This bug disappeared after restart Gnome session.
... I've just noticed that issue doesn't occurred if you use wayland as graphic server but on my archlinux box, as I wrote , I usually use X.org due to some issue with wayland... btw the simple restart of gnome-session or X session doesn't solve the issue (at least for me) Andrea
(In reply to Strangiato from comment #1) > just updated to gtk 3.22.25 on my Arch. > This bug disappeared after restart Gnome session. What backend(s) have you observed this on?
(In reply to Daniel Boles from comment #3) > (In reply to Strangiato from comment #1) > > just updated to gtk 3.22.25 on my Arch. > > This bug disappeared after restart Gnome session. > > What backend(s) have you observed this on? During update process I was running X11. After update I restarted Gnome using Wayland. Currently I can confirm the bug described here under X11. No problem under Wayland.
Reverting 7961e61c3b9e052b0725ccf28665796a7d467e43 fixes this for me.
The gtk behavior changed here, because the previous behavior was wrong. This will likely require changes on the control-center side.
Bug 788206 has a patch *** This bug has been marked as a duplicate of bug 788206 ***