incorrect mount timeout when no user intervention

[Kevin Hunter]

Binary package hint: gvfs

Mounting a file system times out, when (forgetful) user-intervention is required.

Steps to reproduce:

1. Create a partition on your local hard drive, something that nautilus will place under "Places" in the left pane.

2. Click on it, so that Nautilus tries to mount it.
  -- You should be presented with an "Authenticate" dialog --

3. Intentionally "forget" about the box, and don't enter a password.

In a few seconds, you should see an "Unable to mount ... " dialog box, with the error message

"DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible ..."

I believe this dialog box should not appear. In this case, the delay is not a failure of the system or hardware, but of the user to type a password.

Possible remedies:
- Include a (visible) timer so as to remove the dialog box if there is no interaction.
- Leave the dialog box there.

Either way, the NoReply error message is unnecessary in this known context.

[Kevin Hunter (hunteke)]

This is obviously a low-priority bug.

[Kevin Hunter (hunteke)]

This is likely related to https://bugs.launchpad.net/ubuntu/+bug/288543.

However, I claim it is unique because the behavior in this case should instead either have no timeout, or should timeout and remove the user interface part.

[Kevin Hunter (hunteke)]

$ uname -a
Linux hani 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 8.10
Release: 8.10
Codename: intrepid

[Sebastien Bacher (seb128)]

Thank you for your bug report, do you get the issue every time? Could you try on jaunty? That seems to work correctly there

[Kevin Hunter (hunteke)]

1. Yes, every time.

2. Just tried on Jaunty. The issue is still there, although it takes a *much* longer time to reach it: It takes 300 seconds to timeout.

Now, it correctly removes the interaction dialog (user credentials), but still has the explanation dialog. I think the reaction from Ubuntu in this particular use case should just remove the interaction and be done. When it's clear that the user just forgot about it, there's no need to clutter the interface with Yet Another box saying what happened.

This is a semi-cosmetic thing, so no big deal really, but I can't imagine it would be that hard to either add a timeout function to just make it disappear, or to not have it timeout at all.

Tangentially, the Intrepid version did at least give possible reasons, which for other NoReply reasons, is a good thing. Jaunty now has *just*:

DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

[Sebastien Bacher (seb128)]

The bug has been sent on http://bugzilla.gnome.org/show_bug.cgi?id=578151