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 615505 - Remote desktop background images should always be copied to user's home directory
Remote desktop background images should always be copied to user's home direc...
Status: RESOLVED DUPLICATE of bug 143112
Product: gnome-control-center
Classification: Core
Component: Background
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-04-12 09:26 UTC by Morten Egelund Rasmussen
Modified: 2010-04-13 08:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Morten Egelund Rasmussen 2010-04-12 09:26:02 UTC 
Hi there,

I have a machine (Ubuntu 2009.10) that uses a few NFS mounts. All NFS mounts are mounted through autofs, and the NFS server isn't always turned on.

I have selected an image on one of these mounts as the desktop background.

When the NFS server is turned off, and I turn on the client machine, the desktop is just black (and no icons) and the file manager hangs.

Here's my request: If a non-local file is selected as desktop background, it is automatically copied to a folder (file) under the current user's home directory.

If you don't vouch for that idea, the desktop and file manager should at least not hang.

Best regards,

Morten :-)
Comment 1 Vincent Untz 2010-04-12 21:01:16 UTC 
Something that should be done by the capplet, I guess.
Comment 2 Jens Granseuer 2010-04-13 07:54:32 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 143112 ***
Comment 3 Morten Egelund Rasmussen 2010-04-13 08:22:24 UTC 
Wow... A 6 year old bug that is still marked as NEW.... :-/

At least its good that you can find the duplicate bugs. Nice archeology.