After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 743555 - Reconnceting to sftp shows "Could not display""" error
Reconnceting to sftp shows "Could not display""" error
Status: RESOLVED DUPLICATE of bug 693950
Product: nautilus
Classification: Core
Component: File and Folder Operations
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-01-26 20:50 UTC by Konstantinos Tampouris
Modified: 2016-06-09 11:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Konstantinos Tampouris 2015-01-26 20:50:32 UTC 
I use Nautilus -> "Browse Network" to connect to a remote computer using sftp (OpenSSH) and normal password authentication.

The first time I try, I'm able connect to the remote computer without problems.
Then I unmount the share using the eject button.

If I try to reconnect to the share using "Browse Network", I get the message:
"Could not display "". The file is of an unknown type"

(Some times reconnecting to the share succeeds once, but after disconnecting again and trying to reconnect, the above message is displayed.)

If, after this, I try to connect to the remote computer using "Connect to Server", Nautilus crashes with the message:
"ERROR:nautilus-bookmark.c:349:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->details->file))"

If I open Nautilus again, then I am able to connect to the remote computer without problems (the first time) using "Browse Network".
Comment 1 Bastien Nocera 2016-06-09 11:20:55 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 693950 ***