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 523980 - Give the user the opportunity to unmount removable media when moved to Trash
Give the user the opportunity to unmount removable media when moved to Trash
Status: RESOLVED DUPLICATE of bug 115763
Product: nautilus
Classification: Core
Component: Trash
2.20.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-23 14:02 UTC by Uno Engborg
Modified: 2008-04-05 12:04 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Uno Engborg 2008-03-23 14:02:46 UTC
Old MacOS users is used to unmount removable media by dragging it to the Trash.
When they try that in Gnome (tested in Fedora 8), they get an error message saying something like:


"You can't move volume X to the trash. If you would like to unmount it, use the right mouse menu button and select 'unmount volume'"

Wouldn't it be much better if he got a dialog saying "You can't move this volume to trash. Would you like to eject it?" and then have two buttons "Eject"
and "Cancel".

This would be much more forgiving, as the user could continue and get what he most likely wanted to be done, done just by clicking on a button. Instead of clicking on a button, finding the icon again and pulling down the right menu button and finally select "Eject" or "Unmount" or whatever they are called in his language.

If we know enough to present an error message, telling the user what he can't do and how to do it, we should be able to help him do it more directly.



Other information:
Comment 1 Cosimo Cecchi 2008-04-05 12:04:28 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 115763 ***