Bug#800941: regression in 2.46: can't restore a just-trashed file

[Vlad Orlov]

Source: glib2.0
Version: 2.46.0-2
Severity: critical
Justification: breaks functionality of many file managers

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=749314
Control: tags -1 stretch sid upstream
Control: affects -1 caja nemo nautilus thunar


Steps to reproduce:
1. Move some file to trash using a file manager or gvfs-trash tool.
   Tested with the following file managers: Caja, Nemo, Nautilus, Thunar.
2. Browse trash and try to restore the file.

The file manager complains that it can't determine the original location
of the file, and so doesn't restore it. This is a regression in 2.46 since
restoring worked fine in 2.44.

The problem is that "trash::orig-path" and "trash::deletion-date" attributes
are not added to the trashed file. Without that the file manager can't
determine the original location of the file, and hence can't restore it.

You can check the file attributes by printing the moved file's info:
gvfs-info trash:///file_name

Check the upstream report [1] for more details.


[1] https://bugzilla.gnome.org/show_bug.cgi?id=749314