Tested some more locally and the above fix solves half the problem. The other half of the problem is that the gvfs trash daemon creates a .Trash directory inside mount points.
This problem can be worked around entirely using the following workaround: sudo killall -STOP gvfs-gdu-volume-monitor gvfsd-trash We use the above workaround in the Chrome OS build system to ensure that gvfs doesn't mess with our loop devices. There must be a better way... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010141 Title: gvfs-gdu-volume-monitor automounts loop devices, preventing them from being unmounted To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1010141/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
