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 611045 - Connect button is disabled when workgroup is empty
Connect button is disabled when workgroup is empty
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: .General
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2010-02-25 07:24 UTC by Oxmosys
Modified: 2018-02-10 03:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Oxmosys 2010-02-25 07:24:23 UTC
When mounting a samba share with nautilus, if the share doesn't require any username/password, it is immediately mounted, otherwise nautilus asks you three things :

username
workgroup
password

Since the server require authentication, there is no situations where the username can be blank. However, mistakes in the workgroup in most situations won't prevent the connexion and some server don't use password, therefore blank workgroup and blank passwords can be tolerated.

At the moment, nautilus accept blank password, however it does not accept blank workgroup : the "Connect" button stay disabled until something is typed in the workgroup box.

For the reasons above, I think that this "policy" could change to make nautilus mount more user friendly for home users that generally don't use workgroups without breaking the functionnality for profesionnal users.

Steps to reproduce :

1. Have a server with a SMB share protected by a password.
2. Open nautilus and type the smb share adress in the adress bar (ex. : smb://192.168.1.100/share)
3. Type your username and password and blank the workgroup field, if it is not already blank.

Result : You can't connect, the button is disabled.

Expected : It should still be possible to click the connect button, as long as there is something in the username field.
Comment 1 Cosimo Cecchi 2012-05-03 04:37:55 UTC
-> gtk+

That dialog is triggered by GtkMountOperation
Comment 2 Matthias Clasen 2018-02-10 03:26:15 UTC
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.