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 674317 - Clicking symlink to a non-mounted disk gives misleading error message
Clicking symlink to a non-mounted disk gives misleading error message
Status: RESOLVED DUPLICATE of bug 591647
Product: nautilus
Classification: Core
Component: Trash
3.2.x
Other Linux
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-04-18 10:52 UTC by Vadim Rutkovsky
Modified: 2013-04-26 11:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vadim Rutkovsky 2012-04-18 10:52:27 UTC
Original report: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/984356

If you have a symlink to a disk that is not auto-mounted, then clicking on it gives an error message like "The Link "My Pictures" is Broken. Move it to the Rubbish Bin? This link cannot be used, because its target "/media/Acer/Users/Steven/Pictures/My Pictures" doesn't exist."

For a beginner this message is startling, and suggesting that it should be deleted worrying, and not particularly helpful.

The best option from a usability point of view would be to mount the disk, but I bet that's hard to do.

Second best, do not offer to delete it, and say something along the lines of "The file or directory that "My Pictures" links to (/media/Acer/Users/Steven/Pictures/My Pictures) is not currently available. You should check that the disk is mounted."
Comment 1 André Klapper 2012-04-18 13:06:32 UTC
Most users have never heard of mouting either, I guess...
Comment 2 António Fernandes 2013-04-26 11:24:54 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 591647 ***