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 758243 - [Network] cannot abort connecting to a server
[Network] cannot abort connecting to a server
Status: RESOLVED DUPLICATE of bug 764979
Product: nautilus
Classification: Core
Component: general
3.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-11-17 20:39 UTC by Christian Stadelmann
Modified: 2017-08-28 22:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christian Stadelmann 2015-11-17 20:39:59 UTC
Steps to reproduce:
1. open nautilus
2. activate "Other locations"
3. in "Enter server address" (bottom edge) insert a sftp URL to any server that will take a long time to response or let your connection time out. E.g.: sftp://user@example.com
4. press "Connect"
5. press "Abort"

What should happen:
Connection should be aborted freeing resources and UI. It should work as if you were running ssh on terminal and pressed Ctrl+C.

What happens:
Nautilus/gvfs/whatever still tries to connect and doesn't abort. The "Connect to server" feature of nautilus is rendered unusable until connection fails e.g. by timeout. I checked with ssh on terminal: Nautilus seems to be busy for the same duration that ssh will take before returning when trying the same login on the same server.

Affected versions:
nautilus-3.18.2-1.fc23.x86_64
gvfs-1.26.2-1.fc23.x86_64
glib2-2.46.2-1.fc23.x86_64
Comment 1 Christian Stadelmann 2016-03-05 15:53:36 UTC
This issue also affects connecting to a ftps:// server. Changing title to reflect general problem.
Comment 2 António Fernandes 2017-08-28 22:22:45 UTC
Thanks for the bug report!

Good news, this bug was fixed in the meantime in a duplicate report.

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