Erroneous mount error when mounting large (1TB) volume over slow (USB1.1) bus due to DBus timeout
Submitted by Thomas Koster
Assigned to gvf..@..e.bugs
Link to original bug (#557835)
Description
Please describe the problem: Nautilus is prematurely (and incorrectly) reporting that it failed to mount my 1TB external HDD because DBus times out waiting for a reply. Even though the mount is eventually successful, it's a large NTFS volume over a slow bus (USB1.1) so the mount takes a little longer than most other mounts (manually mounting with mount takes just as long), causing DBus to raise a 'No Reply' error prematurely. There don't appear to be any other effects.
Not sure which package is responsible but I was directed to gvfs by the Ubuntu bug team.
Steps to reproduce:
- Connect external HDD and let it automount.
Actual results: Nautilus reports this error: Unable to mount 1000.2 GB Media DBus error org.freedesktop.DBus.Error.NoReply: 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.
The mount is in fact successful after a few seconds longer.
Expected results: No error unless there really is an error mounting the filesystem.
Does this happen every time? Yes.
Other information: Perhaps, instead of reporting an error when DBus times out waiting for a reply, bring up a 'Waiting...' dialog like metacity shows when an application is taking too long to close, just in case nothing is wrong and things are just slow.
Version: 1.0.x