GNOME Bugzilla – Bug 756659
Nautilus's Connect to server wont honor remote path
Last modified: 2017-08-29 14:43:55 UTC
Attempting a connection to a remote SFTP location in the 'Other Locations' field in Nautilus results in undesired action. If I type 'sftp://root@192.168.1.2/data', Nautilus will connect, but drop me into Root's home folder. I then have to go through the labor to make visible the "Enter the Location" feature in Nautilus to type the correct path. If this is by design, it is highly unintuitive.
I'm seeing this too with nautilus 3.18.1 on Fedora 23.
Created attachment 321853 [details] [review] gtkplacesview: use location instead of the enclosing one We were using the enclosing location when connecting to a server, so for instance if we were connecting to ftp://test/test it would actually open ftp://test/ instead of the full path. To fix it, use the full location when emitting the open location signal.
Created attachment 321854 [details] [review] placesview: update to master
Review of attachment 321853 [details] [review]: sure, if it a) works in the file chooser as well b) works for all protocols I have no idea why the enclosing location thing was there, maybe there's a reason ?
(In reply to Matthias Clasen from comment #4) > Review of attachment 321853 [details] [review] [review]: > > sure, if it a) works in the file chooser as well b) works for all protocols afaik, it does. > > I have no idea why the enclosing location thing was there, maybe there's a > reason ? I don't know. It was not like that in Nautilus [0]. [0] https://git.gnome.org/browse/nautilus/commit/?id=474a6c2aa025fcd94bff50e3501a2eb41e4f0388
Attachment 321853 [details] pushed as 17a4bd5 - gtkplacesview: use location instead of the enclosing one
Comment on attachment 321854 [details] [review] placesview: update to master Attachment 321854 [details] pushed as 4b8c6ec - placesview: update to master
*** Bug 760799 has been marked as a duplicate of this bug. ***
(In reply to Matthias Clasen from comment #4) > I have no idea why the enclosing location thing was there, maybe there's a > reason ? The reason was bug 522917. In short: if trying to connect to a server without a specific path, it would try to open the root path, which may not be accessible to the user, in which case connecting to user home is a more helpful fallback than an error message. I don't have a server to test, but that bug may have been reintroduced by fixing this one.
*** Bug 766894 has been marked as a duplicate of this bug. ***