After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 729910 - Desktop wallpaper change does not take place immediately
Desktop wallpaper change does not take place immediately
Status: RESOLVED DUPLICATE of bug 710756
Product: gnome-shell
Classification: Core
Component: background
3.12.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2014-05-10 08:57 UTC by Aman Raj
Modified: 2014-11-07 10:37 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
I changed my wallpaper to one shown in Work (i.e black and white image with Linux written on it)space but it didn't change on my desktop. (664.76 KB, image/png)
2014-05-10 08:57 UTC, Aman Raj 		Details

Description Aman Raj 2014-05-10 08:57:43 UTC 
Created attachment 276275 [details]
I changed my wallpaper to one shown in Work (i.e black and white image with Linux written on it)space but it didn't change on my desktop.

Changing the desktop wallpaper needs a restart. While this change take place immediately in Work space but needs a restart to have change on desktop.
Comment 1 Claes Comly 2014-05-27 10:48:04 UTC 
same here, archlinux 64bit, gnome 3.12. Have to relog to change background. Work spaces shows the correct background.
Comment 2 lvl70nub 2014-08-26 11:46:23 UTC 
I have a very similar problem. The background gets stuck instantly second monitor and occasionally on my primary monitor. I need to restart gnome window manager (alt+f2 r enter) to get it to change. 

Work spaces shows the correct background. The background also changes when I go to Activities then changes back when I leave it.
Comment 3 Bastien Nocera 2014-11-07 10:37:26 UTC 
This looks like a duplicate of bug 710756 which got fixed in 3.14.1.

Please reopen this bug, or file a new one if you can still see problems in
3.14.1.

*** This bug has been marked as a duplicate of bug 710756 ***