desktop-packages team mailing list archive

[Monsta <1495943@xxxxxxxxxxxxxxxxxx>]

Thanks, restoring from trash works now. Not sure why the linked Debian
bug isn't closed yet... the fix made it into Unstable before Wily
anyway.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1495943

Title:
  gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in gvfs package in Ubuntu:
  Fix Released
Status in glib2.0 package in Debian:
  Confirmed

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::deletion-date attributes to it. 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:///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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1495943/+subscriptions