> You can do "sudo killall udisks-daemon" > and log out, and check if the next login then behaves like the initial > one.
Yes, your assumption is correct. At the next login nautilus runs the the mount command, which takes 18 minutes to complete. > Likewise, it's interesting to check whether a mere > > sudo killall udisks-daemon > udisks --dump > > triggers floppy access. Yes, it triggers floppy access. But it takes "only" 25 seconds until it fails. Only one I/O error is written to syslog. No mount process is spawned. The next attempt succeeds immediately. geu...@geuder-t40-u:~$ time udisks --dump (udisks:2373): udisks-WARNING **: Couldn't enumerate devices: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. real 0m25.038s user 0m0.012s sys 0m0.000s geu...@geuder-t40-u:~$ time udisks --dump ======================================================================== Showing information for /org/freedesktop/UDisks/devices/fd0 ... output deleted ... ======================================================================== real 0m0.308s user 0m0.104s sys 0m0.012s -- Attempts to mount floppy despite no media present - disable automount https://bugs.launchpad.net/bugs/539515 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
