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 329025 - Feedback needed for "Connect to a server" dialog responses.
Feedback needed for "Connect to a server" dialog responses.
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.22.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 449571 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-01-29 00:18 UTC by Alban Crequy
Modified: 2010-07-05 23:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Alban Crequy 2006-01-29 00:18:44 UTC
Forward bug report from:
https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/29391

I click on "Connect to a server" in the "shortcuts" Gnome menu and then I
fillfull the form and click on "Connect".

And I wait but nothing happen: no window explain me the connection has failed.
And a long time after, I realized that an icon has been added on the desktop. I
cannot see it sooner because others windows hide it.

And I realized that the aim of this form is not to connect to a server but to
add a shortcut on the desktop.

I suggest the following:
 - The button name of the form must not be called "Connect" because it does not
connect when I click on it. Call it for example "Add the shortcut on the desktop".
 - When the user click on this button, show a little dialog window explaining:
"An icon shortcut has been successfully added on your desktop. You can see it if
you hide all others windows". Without this explanation, how can the user know
that the form just does not work?

Other information:
I use GNOME 2.12.1 with Ubuntu 5.10.
Comment 1 Lakin Wecker 2006-02-17 18:32:52 UTC
It does try to open the folder.  In Ubuntu breezy(nautilus-2.12.x) it frequently does not. 

I just tested this in dapper(nautilus-2.13.91), and it does one of two things:  
1) Successfull connection, it opens the folder.
2) Unsuccesfull connection, it shows an error dialog.

However, there still is the problem that there is no feedback during the process, even if it takes a while (2-15seconds) for either the error or the connection, there is no feedback.  

If the folder can be shown immediately, with the throbber loading or some sort of connection status indictation, then the user knows that something is going on.
Comment 2 bill.haneman 2006-02-20 14:35:10 UTC
sorry, not sure what component to assign this to, but certainly not "Accessibility".  THanks.
Comment 3 Patrick Wagstrom 2006-11-01 20:10:44 UTC
I can confirm that this problem is still present in Nautilus 2.16 on Ubuntu Edgy.    I did some debugging on this from the server end and found that Nautilus is not even trying to connect to the server.

Still a problem.  Bumping version numbers and marking it as "File and Folder Operations" for component and bumping version number to 2.16.x.
Comment 4 Patrick Wagstrom 2006-11-01 20:12:15 UTC
Also, can someone confirm if this problem is present on platforms other than Ubuntu?  It seems like all three people reporting the bug so far have been using Ubuntu.
Comment 5 Jens Granseuer 2006-11-10 12:13:54 UTC
Yes, I can confirm this is also the case in the stock (upstream) version, and I also found the dialog very confusing the first time I used it. However, I don't think it's a real (like in programming error) bug. AFAICS, the dialog isn't actually supposed to open the connection, but only add the connection icon to the desktop. As such, the real issue is probably just a matter of using some better wording in the dialog, so users know what to expect. So, basically, I guess I agree with the original poster.
Comment 6 Brett Alton 2007-06-20 19:07:03 UTC
I have a similar bug here: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/120220 - "Connect to server" have minimal dialogues - Needs to communicate more
Comment 7 sam tygier 2007-09-24 17:10:49 UTC
also see http://bugzilla.gnome.org/show_bug.cgi?id=449571
these are duplicates
Comment 8 Cosimo Cecchi 2008-03-16 11:45:50 UTC
*** Bug 449571 has been marked as a duplicate of this bug. ***
Comment 9 Cosimo Cecchi 2008-03-16 12:14:42 UTC
Modifying fields, this is still valid with 2.22. Also, CC-ing Vincent.

I think it would be nice to:
- not hide the dialog after clicking on connect
- instead, make the dialog insensitive
- have a little animation at the bottom of the dialog with a "Connecting..." label or sth similar
- hide the dialog on a successful mount or only when an error pops up or (even better) eliminate the separate error widget and report errors at the bottom of the dialog, making the widget sensitive again.
Comment 10 Brett Alton 2008-07-26 14:57:59 UTC
I'm quite sure this was fixed in 2.22. Once you hit 'connect', it opens up Nautilus, or explains why it can't connect. It also gives you the option to connect once, or save it as a bookmark.

I'd say my complaints were met and fixed here.

Please close.
Comment 11 Marcus Carlson 2010-07-05 21:50:49 UTC
Cosimo, should we close this bug as Brett says or do you still want it open to make the changes you suggest?
Comment 12 Cosimo Cecchi 2010-07-05 23:12:39 UTC
No, let's close this as OBSOLETE.