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 538020 - dragging volume to trash provides even less helpful response
dragging volume to trash provides even less helpful response
Status: RESOLVED DUPLICATE of bug 525480
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.22.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-12 16:44 UTC by Julian Andres Klode
Modified: 2008-06-12 16:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Julian Andres Klode 2008-06-12 16:44:41 UTC
The following bug has been reported in Debian at 
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478289


This is the content of the bug report:

Subject: nautilus: dragging volume to trash provides even less helpful response

Attempting to drag a volume to the trash no longer provides the
(unhelpful and annoying) message that you should use Eject instead; now
it claims:

  Error while deleting.

  There was an error getting
  information about "Audio Disk.volume".

  > Show more details
  The specified location is not supported

Although I am of the opinion that dragging a volume to the trash should
eject the volume, because that's what everyone who does that expects it
to do, the current situation is a regression in helpfulness.  "The
specified location is not supported" is not at all helpful, and wouldn't
mean anything to me if I hadn't already known that nautilus doesn't
support trash-to-eject.

Please fix it to either restore the old message or support
trash-to-eject.



Other information:
Comment 1 Cosimo Cecchi 2008-06-12 16:59:35 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 525480 ***