Able to reproduce in Precise.
** Changed in: nautilus (Ubuntu)
Status: Expired => Confirmed
** Bug watch added: GNOME Bug Tracker #668871
https://bugzilla.gnome.org/show_bug.cgi?id=668871
** Also affects: nautilus via
https://bugzilla.gnome.org/show_bug.cgi?id=668871
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/666863
Title:
Nautilus sftp suspend
Status in Nautilus:
Unknown
Status in “nautilus” package in Ubuntu:
Confirmed
Bug description:
Binary package hint: nautilus
When connected to sftp, nautilus behaves unpredictable after a
suspend/wakeup cycle. Just now I was connected to a sftp-server at work. I put
the laptop in suspend, went home, and then woke the computer again. The
sftp-connection is displayed as still active. When I press the reload-button in
nautilus, the file-manager hangs for approx 60 seconds. Then it fails to
reload, with the following two error-messages:
- The folder contents could not be displayed.
Sorry, could not display all the contents of "category": 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.
... and ...
- Could not display
"sftp://utv...@utvikling.arcg...ner/html/com_content/category";.
Error: 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.
Please select another viewer and try again.
Clicking the unmount-icon in nautilus, and the reconnecting, nautilus
connects without problems.
However, I have experienced that a shorter/different suspend/awake-
cycle might give a different result.
Expected result: Trying to reload a folder should ultimately try to
disconnect and reconnect the connection if the connection is broken.
Alternatively, nautilus should fail gracefully with a single,
understandable error message.
regards Jonas
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nautilus 1:2.30.1-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Oct 26 17:50:20 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: nautilus
To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/666863/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
