gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GLib |
Fix Released
|
Critical
|
|||
glib2.0 (Debian) |
Fix Released
|
Unknown
|
|||
glib2.0 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
gvfs (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
[System]
Ubuntu MATE 15.10, fully updated.
[Steps to reproduce]
1. Create an empty file: touch ~/test
2. Move it to trash: gvfs-trash ~/test
3. Launch some file manager, browse Trash folder and try to restore the file. I've tested it with the following file managers: Caja, Nemo, Nautilus and Thunar.
[Expected result]
The file should be restored to its original location.
[What happens instead]
The file manager complains that it can't determine the original location of the file, and so doesn't restore it.
[Details]
When moving file to Trash, gvfs-trash does not add trash::orig-path and trash::
You can check the file attributes by printing the moved file's info:
gvfs-info trash:///test
[Regression description]
Restoring the files has been working fine in Ubuntu 14.04 and 15.04. This bug appeared only in 15.10, so it's a regression.
You can see the gvfs-info output from 15.04 and 15.10 in the attachments below.
Changed in gvfs (Ubuntu): | |
importance: | Undecided → Critical |
Changed in gvfs (Ubuntu): | |
importance: | Critical → High |
assignee: | nobody → Ryan Lortie (desrt) |
tags: | added: rls-w-incoming |
Changed in glib: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
Changed in glib: | |
importance: | Medium → Critical |
status: | Confirmed → Incomplete |
no longer affects: | glib2.0 (Debian) |
Changed in glib2.0 (Debian): | |
status: | Unknown → Confirmed |
Changed in glib: | |
status: | Incomplete → Fix Released |
Changed in gvfs (Ubuntu): | |
status: | Confirmed → Fix Committed |
assignee: | Allison Ryan Lortie (desrt) → nobody |
Changed in glib2.0 (Debian): | |
status: | Confirmed → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.