Any chance you can confirm that downgrading to gvfs 1.18.0 fixes this again, i. e. that the regression is in 1.18.1? You can get the old binaries from https://launchpad.net/ubuntu/+source/gvfs/1.18.0-0ubuntu1, click on your architecture, download the debs and install them with "sudo dpkg -iO *.deb".
Once that's confirmed, we need to find out which particular commit broke it. There aren't too many relevant ones between .0 and .1, the most plausible one is https://git.gnome.org/browse/gvfs/commit/?id=3448fa01d5 . Perhaps nautilus and thunar use the gvfs API differently so that the lock doesn't happen in GNOME (trash works fine here). Any chance that you could try to reverse-apply that patch, build, and check if the lock goes away?
Any chance you can confirm that downgrading to gvfs 1.18.0 fixes this again, i. e. that the regression is in 1.18.1? You can get the old binaries from https:/ /launchpad. net/ubuntu/ +source/ gvfs/1. 18.0-0ubuntu1, click on your architecture, download the debs and install them with "sudo dpkg -iO *.deb".
Once that's confirmed, we need to find out which particular commit broke it. There aren't too many relevant ones between .0 and .1, the most plausible one is https:/ /git.gnome. org/browse/ gvfs/commit/ ?id=3448fa01d5 . Perhaps nautilus and thunar use the gvfs API differently so that the lock doesn't happen in GNOME (trash works fine here). Any chance that you could try to reverse-apply that patch, build, and check if the lock goes away?