Hmm, this bug is assigned to gvfs. I must admit that I understand gvfs less then well. But according to my analysis https://bugs.launchpad.net/bugs/586873 gvfs was not involved in this issue.
nautilus just calls /bin/mount (see http://launchpadlibrarian.net/49269052/pstree2.txt ) with a single parameter /media/floppy (see https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/586873/comments/5 ). And that mount command does not finish for 20-30 minutes, error messages are written all the time to /var/log/syslog (see https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/586873/comments/2 )
Not sure whether
a.) nautilus should never have called mount or b.) mount should fail immediately
But at least I don't see how gvfs is involved here.
Hmm, this bug is assigned to gvfs. I must admit that I understand gvfs less then well. But according to my analysis https:/ /bugs.launchpad .net/bugs/ 586873 gvfs was not involved in this issue.
nautilus just calls /bin/mount (see http:// launchpadlibrar ian.net/ 49269052/ pstree2. txt ) with a single parameter /media/floppy (see https:/ /bugs.launchpad .net/ubuntu/ +source/ nautilus/ +bug/586873/ comments/ 5 ). And that mount command does not finish for 20-30 minutes, error messages are written all the time to /var/log/syslog (see https:/ /bugs.launchpad .net/ubuntu/ +source/ nautilus/ +bug/586873/ comments/ 2 )
Not sure whether
a.) nautilus should never have called mount or
b.) mount should fail immediately
But at least I don't see how gvfs is involved here.