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 756659 - Nautilus's Connect to server wont honor remote path
Nautilus's Connect to server wont honor remote path
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: .General
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
: 760799 766894 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2015-10-15 17:31 UTC by zachary.sandberg
Modified: 2017-08-29 14:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gtkplacesview: use location instead of the enclosing one (1.42 KB, patch)
2016-02-22 15:26 UTC, Carlos Soriano
committed Details | Review
placesview: update to master (1.16 KB, patch)
2016-02-22 15:26 UTC, Carlos Soriano
committed Details | Review

Description zachary.sandberg 2015-10-15 17:31:00 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.
Comment 1 Teppo Turtiainen 2015-11-04 11:07:59 UTC
I'm seeing this too with nautilus 3.18.1 on Fedora 23.
Comment 2 Carlos Soriano 2016-02-22 15:26:13 UTC
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.
Comment 3 Carlos Soriano 2016-02-22 15:26:32 UTC
Created attachment 321854 [details] [review]
placesview: update to master
Comment 4 Matthias Clasen 2016-02-22 21:25:22 UTC
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 ?
Comment 5 Carlos Soriano 2016-02-23 09:12:51 UTC
(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
Comment 6 Matthias Clasen 2016-02-24 01:44:07 UTC
Attachment 321853 [details] pushed as 17a4bd5 - gtkplacesview: use location instead of the enclosing one
Comment 7 Carlos Soriano 2016-02-24 10:24:56 UTC
Comment on attachment 321854 [details] [review]
placesview: update to master

Attachment 321854 [details] pushed as 4b8c6ec - placesview: update to master
Comment 8 António Fernandes 2017-08-28 09:30:34 UTC
*** Bug 760799 has been marked as a duplicate of this bug. ***
Comment 9 António Fernandes 2017-08-28 09:37:30 UTC
(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.
Comment 10 António Fernandes 2017-08-29 14:43:55 UTC
*** Bug 766894 has been marked as a duplicate of this bug. ***