[Hardy] Nautilus freezes at open volume mounted before suspend

Bug #204254 reported by Liken Otsoa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

I have a SSH volume mounted (SFTP://).

After suspend to Ram and Resume if you try to Open this Volume Nautilus Freezes.
I think with a samba volume is equal.

Another problems:

1. If I have a launcher icon: SFTP://MyServer/Stock, when I launch it why does nautilus create another volume icon at main SFTP://MyServer?. Similar with Samba, I finish always with duplicate icons at desktop. And a Launcher is the only way to preserve a link in desktop between sessions.

2. Is there any method to create a link to a network shared directory. I Need to do it manually. I think this is far to be for human beings :) .

_________________
Hardy, uptodate
IBM Thinkpad X41 Tablet

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace of the hang http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in nautilus:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in nautilus:
status: Incomplete → Invalid
Revision history for this message
chris4585 (chris4585) wrote :

@Pedro will this information help any?

chris@ubuntu:~$ nautilus

(nautilus:6679): Unique-DBus-WARNING **: Error while sending message: 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.

(nautilus:6679): Unique-DBus-WARNING **: Error while sending message: 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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.