As a follow up, it looks like the server to which the user was connecting was leaving sftp-server processes running.
Another issue was the user's bashrc was printing some extra characters to screen even when connecting to sftp - so nautilus was bugging out on that. I had originally thought this was a nautilus error but it looks more like there was an issue on the server than with the client machine. Christopher Tooley [email protected] Systems, HEP/Astronomy UVic On 2012-07-30, at 5:05 PM, Christopher Tooley <[email protected]> wrote: > Hello all, > > It looks like one of my SL6.2 machines is not correctly hooking up with dbus > - a user has some bookmarks defined as sftp links, and they are no longer > working after a restart on the weekend. > > The error reported is: > "Could not open location 'sftp://<user>@<remote>/<dir>' > 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." > > Is this a known problem, and is there a fix, or is this more likely something > on my end (I don't have access to the server the user is attempting to access > with sftp, so I can't test other systems very well) > > Thanks, > Chris
