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 692962 - "Set as wallpapers" options create multiple copy of the same image in the $HOME/Pictures/Wallpapers dir
"Set as wallpapers" options create multiple copy of the same image in the $HO...
Status: RESOLVED DUPLICATE of bug 688812
Product: nautilus
Classification: Core
Component: general
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-01-31 19:18 UTC by Andrea Antolini
Modified: 2013-02-02 14:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andrea Antolini 2013-01-31 19:18:35 UTC
browse your picture repository and select an image choosing  "Set as wallpaper" from the context menu

If doesn't exist, the folder $HOME/Pictures/Wallpapers is created and a copy of original image is placed in that directory. I guess, the copied image  is used as wallpaper.. this could be acceptable even if a sort of softlink could be used instead of  generate a 2nd copy of the original image..

Anyway, if you go into the $HOME/Pictures/Wallpapers, choose the image and select again "Set as wallpaper" another  copy of the same image is created in the folder..

if you choose the new copy of image,  select  "Set as wallpaper" another copy of the copy image is created in the folder..

and so on..

I think that  should be managed in a better way an existing image already present in the $HOME/Pictures/Wallpapers avoiding the creation of multiple copies of the same image...

Cheers
Andrea
Comment 1 António Fernandes 2013-02-02 14:40:48 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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