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 159727 - Changing desktop wallpaper doesn't work
Changing desktop wallpaper doesn't work
Status: RESOLVED DUPLICATE of bug 154005
Product: nautilus
Classification: Core
Component: Desktop
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-11-28 15:07 UTC by Vincent van Adrighem
Modified: 2005-02-03 12:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description Vincent van Adrighem 2004-11-28 15:07:39 UTC 
Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.8.1 unspecified
Gnome-Distributor: Debian
Synopsis: Changing desktop wallpaper doesn't work
Bugzilla-Product: nautilus
Bugzilla-Component: Desktop
Bugzilla-Version: unspecified
Description:
Description of Problem:

The selected wallpaper isn't shown until you logoff and logon again, or
kill nautilus.

Steps to reproduce the problem:
1. Select a new wallpaper with the wallpaper thingy.

Actual Results:

Not activated until nautilus is restarted

Expected Results:

Instant apply

How often does this happen?

Always, but after a kill of nautilus, it does apply instantly.

Additional Information:




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-28 10:07 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "nautilus".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 Sebastien Bacher 2005-02-03 12:14:42 UTC 
this issue is due to gconf: http://bugzilla.gnome.org/show_bug.cgi?id=154005

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