gio trash (or gvfs-trash) on a vboxsf partition fails with "Unable to find or create trash directory"

Bug #1774601 reported by Jon "The Nice Guy" Spriggs on 2018-06-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
glib2.0 (Ubuntu)
Undecided
Unassigned
gvfs (Ubuntu)
Undecided
Unassigned

Bug Description

I am using an Ubuntu 18.04 Vagrant machine, which has had the ubuntu-mate-desktop tasksel applied to it. I mount a filesystem from the Virtualbox Host using this line in /etc/fstab:

    HostHome /HostHome vboxsf _netdev,uid=1000,gid=1000,dmask=0077,fmask=0177 0 0

With this build, I have installed the atom snap package, and when I try to remove a file from the file tree, I get an error saying:

    The following file couldn't be moved to the trash.
    /HostHome/Documents/01 Projects/K5-Ansible-Openstack-Development-Machine/ansible_users.retry
    Is gvfs-trash installed?

On further investigation, I found that while gvfs-trash is installed (via the gvfs-common package), it has been depreciated, preferring gio. Running either `gio trash` or `gvfs-trash` specifying that path (`/HostHome/Documents/01 Projects/K5-Ansible-Openstack-Development-Machine/ansible_users.retry`) returns this report:

    gio: file:///HostHome/Documents/01%20Projects/K5-Ansible-Openstack-Development-Machine/ansible_users.retry: Unable to find or create trash directory for /HostHome/Documents/01 Projects/K5-Ansible-Openstack-Development-Machine/ansible_users.retry

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libglib2.0-bin 2.56.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: MATE
Date: Fri Jun 1 08:26:04 2018
SourcePackage: glib2.0
UpgradeStatus: No upgrade log present (probably fresh install)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers