FS#38853 - [gvfs] org.gtk.vfs.Daemon Unsupported operation detected on trash directory
Attached to Project:
Arch Linux
Opened by Robert Orzanna (orschiro) - Monday, 10 February 2014, 07:04 GMT
Last edited by Jan de Groot (JGC) - Sunday, 18 January 2015, 10:34 GMT
Opened by Robert Orzanna (orschiro) - Monday, 10 February 2014, 07:04 GMT
Last edited by Jan de Groot (JGC) - Sunday, 18 January 2015, 10:34 GMT
|
Details
Description:
I use Thunar as my file manager and gvfs for mounting. Whenever I move a file to trash I get the following error message: Feb 10 07:58:18 thinkpad org.gtk.vfs.Daemon[884]: ** (process:4015): WARNING **: *** Unsupported operation detected on trash directory Feb 10 07:58:18 thinkpad org.gtk.vfs.Daemon[884]: ** (process:4015): WARNING **: dir: /home/orschiro/.local/share/Trash/files, file: treesheets-git.tar.gz, type: 1 Why is moving a file to trash an unsupported operation? Apparently moving to trash is still working: ~ ❯ l /home/orschiro/.local/share/Trash/files/treesheets-git.tar.gz ⏎ -rw-r--r-- 1 orschiro users 959 2014-02-08 11:22:04.176226315 +0100 /home/orschiro/.local/share/Trash/files/treesheets-git.tar.gz Additional info: thunar 1.6.3-1 gvfs 1.18.3-3 gvfs-afc 1.18.3-3 Steps to reproduce: 1. Select a file in Thunar 2. Press `Delete` or right mouse click `Move to Trash` 3. Check error message in journalctl |
This task depends upon
Closed by Jan de Groot (JGC)
Sunday, 18 January 2015, 10:34 GMT
Reason for closing: Fixed
Additional comments about closing: https://bugzilla.gnome.org/show_bug.cgi? id=737473
Sunday, 18 January 2015, 10:34 GMT
Reason for closing: Fixed
Additional comments about closing: https://bugzilla.gnome.org/show_bug.cgi? id=737473
For /home I use ext4:
/dev/mapper/VolGroup00-Home ext4 214557368 158218628 45417248 78% /home
From the source:
g_warning ("*** Unsupported operation detected on trash directory");
if (!already_did_warning)
{
g_warning (" A trash files/ directory should only have files "
"linked or unlinked (via moves or deletes). Some other "
"operation has been detected on a file in the directory "
"(eg: a file has been modified). Likely, the data "
"reported by the trash backend will now be "
"inconsistent.");
already_did_warning = TRUE;
}
gvfs monitors the trash directory. When it receives an event which is different from create, delete, unmount or unmounted, then it generates this warning. If I'm not mistaken, the type=1 operation is G_FILE_MONITOR_EVENT_CHANGES_DONE_HINT, so my guess is that something changed in glib (thunar and nautilus use g_file_trash from glib) which is not handled correctly in gvfs.
Is this something we have to be worried about?