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 753550 - Too hard to access a changing bookmark (that includes an IP address)
Too hard to access a changing bookmark (that includes an IP address)
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: Bookmarks
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-08-12 09:26 UTC by Tomáš Hnyk
Modified: 2017-09-21 18:18 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tomáš Hnyk 2015-08-12 09:26:50 UTC
I run ssh server on my phone that I access it over wifi through a bookmark that has location like "sftp://user@192.168.11.150/media/mmc1". All is well when I am on my home network as dhcp always assignes static addresses there. U just use the bookmark and Nautilus performs wonderfully.

However, once I get to a different network with my laptop, the phone is assigned a different IP adress. I have a widget on the phone that shows me the address, but in Nautilus, I have to go to bookmarks, copy paste the location, rewrite the ip address and put it into location bar.

Much easier would be if
1) I could right click the bookmark and it would allow me to copy its location (or through an edit action- currently I can only rename it, but I am interested in the link itself.)
or 2) after using the bookmark the address would get displayed in the location bar with an error message where I could rewrite it.
3) some other design that would not make this too complicated.

And please do not suggest Bluetooth, that is way to slow for large files.
Comment 1 António Fernandes 2017-08-23 09:58:27 UTC
Hi. Thanks for the feature suggestion.

After you originally reported this, nautilus has got a new "+ Other Locations" feature that might just do what you need.

Steps:
1) Open nautilus. In the sidebar, bellow bookmarks, click on "+ Other Locations".
2) At the bottom of the window you will see a "Connect to Server" bar. Besides it is a field with the hint "Enter server address...". Enter "sftp://user@192.168.11.150/media/mmc1" there then hit the "Connect" button next to it.

3) change to another network that gives a different IP
4) In nautilus, go to "+ Other Locations" again.
5) Next to the "Enter server address..." text field, there is a small button with an arrow/triange. Click on it.
6) It opens a list of recent addresses, including the one you used before. Click on it.
7) The address will be added to the text field and you can edit it from there, then connect.
8) This address will be remembered too.

What do you think? Does this work for your use case?
Comment 2 Tomáš Hnyk 2017-09-20 12:19:35 UTC
Well, yes, that is easier to use than now. I am not sure how well this would work if one uses connect to server often (then the address could easily get dropped off the recent list), but it is good enough for me at this stage and I guess you can close this bug (I would still prefer solution 2) but I understand GNOME design went another way than I would have prefered).
Comment 3 António Fernandes 2017-09-21 09:45:25 UTC
(In reply to Tomáš Hnyk from comment #2)
Thank you for the feedback.

Indeed, the recent list doesn't scale well if a lot of different addresses are often used. But neither did the Bookmarks list. Still, there is room for improvement.
Comment 4 Tomáš Hnyk 2017-09-21 09:51:36 UTC
Well, it scaled well if you needed to bookmark something not frequently used and at the same time used mor often many servers to connect to that kept changing - not my usecase though.
Comment 5 António Fernandes 2017-09-21 10:03:01 UTC
Actually, that's still possible, bookmarking didn't go anywhere. Remote locations can be bookmarked the same way as local folders.
Comment 6 António Fernandes 2017-09-21 18:18:47 UTC
What a coincidence, 2 days ago the same issue was reported on gitlab, but I didn't notice it until now.
https://gitlab.gnome.org/GNOME/nautilus/issues/26