@David: could you reply to Martin's comment and confirm that gvfs doesn't automount the device?
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1010141 Title: gvfsd-trash probes devices not in /run/media, keeping the device busy Status in GVFS: Unknown Status in “gvfs” package in Ubuntu: Triaged Bug description: Right now, if you mount a loop device on Ubuntu Precise, gvfs-gdu- volume-monitor grabs hold of the mount, preventing it from being unmounted. I've attached a script (gvfs-test.sh) which reproduces the problem reliably on Ubuntu Precise. Ubuntu has a setting which should disable this automount behavior, but it doesn't work: I tried setting System Settings -> Details -> Removable Media -> Never prompt or start programs on media insertion, but gvfs-gdu-volume-monitor still grabs hold of loop devices. This bug is present in Ubuntu Precise but is not present in Ubuntu Lucid. With the attached script (gvfs-test.sh), it fails with the following message: + sudo bash -c 'mount /dev/loop0 /tmp/tmp.A8gsvsAc7T-gvfs-test && umount /tmp/tmp.A8gsvsAc7T-gvfs-test' umount: /tmp/tmp.A8gsvsAc7T-gvfs-test: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) Killing gvfs-gdu-volume-monitor works around the problem. You can also work around the bug by sleeping for a few seconds prior to unmounting the loop device. There are two related bugs here: 1) gvfs-gdu-volume-monitor should not be touching loop devices at all -- they are not removable media so they should not be automounted. 2) It should be possible to disable the automount behavior of gvfs-gdu-volume-monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1010141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
