Nautilus should default to copy when move will fail
Bug #773061 reported by
Chris Halse Rogers
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Nautilus |
New
|
Undecided
|
Unassigned | ||
| nautilus (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
Binary package hint: nautilus
Dragging a file from a read-only filesystem currently rightly causes the drop action to be ‘copy’ rather than ‘move’. However, if you drag a file from a location to which you don't have write privileges (so it's read-only because of permissions) Nautilus will by default try and fail to move the file.
Nautilus drag and drop should default to copy when dragging from a source which is read only, regardless of the reason it's read-only.
| Changed in nautilus (Ubuntu): | |
| importance: | Undecided → Wishlist |
Revision history for this message
| Sebastien Bacher (seb128) wrote | #1 |
| Changed in nautilus (Ubuntu): | |
| status: | New → Confirmed |
To post a comment you must log in.
Not sure if it should default to a different action, inconsistency and automagic behaviour changes are not user friendly, but one option would be to display a dialog explaining what the issue is with a "copy instead" button?