GNOME Bugzilla – Bug 659702
Lock screen does not pick the new wallpapers dynamically
Last modified: 2011-09-25 21:38:38 UTC
this report has been filed here: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/850373 g-s version is : 3.1.92 "Steps to reproduce it: 1- Login and do a Lock Screen (Notice that the wallpaper being shown is the same as the one in your desktop) 2- Unlock the screen and change the wallpaper with the gnome-control-center capplet 3- Lock the Screen What happen: The wallpaper being shown there in the lock dialog is the previous one. What should happen: The wallpaper being shown in the lock dialog should match the one in the desktop." Thanks in advance.
That's actually not the current design. The current design is to make the screensaver password screen have the same background as the login password screen (gdm), not the user's background. It doesn't work exactly that way either though since the switchover to dconf, but it's a close approximation to that. The whole screensaver ui is going to be redone for 3.4, so there may be a new design then, though.
That's not really true, gnome-screensaver does pick the user background, if you change it with the control-center and restart gnome-screensaver it displays the new selected one, either it shouldn't or it should do it without needing a restart
the design is for all the unlock dialog background and login dialog background to look the same. That was the intention and how it worked leading up to 3.0. During the gsettings switch over it was changed to pull from the schema instead, since there is no system dconf database that gdm and screensaver could share. The way the code accomplishes this is to freeze gsettings on "org.gnome.desktop.background" with g_settings_delay() and then run g_settings_reset() (with no corresponding g_settings_apply). At least that's how it worked last time I looked. It could be it no longer works that way. Anyway, we'll mop this up when we redesign it I guess.
Looks like the "displays new selected one" is being tracked by bug 649769
thank for the comments, I've no strong opinion on the correct behaviour but either it should track the login screen background and stay to it or track the user one but without requiring a restart, the current behaviour doesn't make sense in any of those ways. So feel free to duplicate it from #649769
*** This bug has been marked as a duplicate of bug 649769 ***