GNOME Bugzilla – Bug 142020
Properties of network volume should have tab for username, password, URI
Last modified: 2012-08-24 20:51:04 UTC
When creating a new network volume on the desktop with 'Connect to server', the user gets only one chance to enter connection properties. I found myself looking in vain for those properties in the properties tab of the mounted volume. If I have made a typo in the password, for instance, it's easier to open the properties of the volume object and change it there, than to delete/unmount the volume and recreate it again. Also it would be more in line with the spatial model to have those properties, since the volume icon *is* the network connection. Having to go to a menu somewhere else to change something breaks the metaphor IMHO.
I completely agree with this and i have run into the issue numerous times. This is especially important because of the finicky nature of windows implementations of the smb protocol over different platforms.
still here with 2.8
*** Bug 304738 has been marked as a duplicate of this bug. ***
*** Bug 308185 has been marked as a duplicate of this bug. ***
*** Bug 311335 has been marked as a duplicate of this bug. ***
*** Bug 324743 has been marked as a duplicate of this bug. ***
updating version fields.
soon this will have two-years-anniversary :-( On IRC it was pointent out to me by kmaraas that it is possible to edit the properties using gconf-editor (/desktop/gnome/connected_servers/) While this is works, this is far from being intuitive.
*** Bug 337174 has been marked as a duplicate of this bug. ***
We need GnomeVFS support for this functionality, see bug 316403.
Ubuntu bug about that: https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/42615 "can't rename network server shortcut After having created shortcuts for example for ssh/sftp, you can't rename them or change other options afterwards. It forces me to 'unmount' the shortcut and rebind again with different options. I expected to be able to do so with the right click properties menu on the desktop."
Given that it is possible to modify the connections using gconf-editor, I really do not understand why there must be support for this by the means of gnome-vfs. Maybe someone could enlighten me..
Christian Lohmaier wrote: "Given that it is possible to modify the connections using gconf-editor, I really do not understand why there must be support for this by the means of gnome-vfs." Because gconf-editor is by design not intended for use by wide majority of users. Most users know nothing about gconf-editor - and they shouldn't need it. IMHO, it is reasonable to expect that for such a basic operatin as changing properties of a connection, there should be a user-friendly and easily discoverable GUI. gconf-editor is neither.
No, the question was not: "why do we need another method besides using gconf-editor", but: "Why do you need gnomevfs to modify gconf-values" If you read the previous comments, you'll notice that I'm not happy with using gconf-editor for this either.
*** Bug 354142 has been marked as a duplicate of this bug. ***
So nobody can explain why gnome-vfs is necessary to modify a gconf-setting...
Updating version fields. Maintainers, please re-target as 2.16 obviously won't have this feature any more.
*** Bug 367431 has been marked as a duplicate of this bug. ***
Still valid.
This bug is still valid with the new gio based nautilus. Except that I can't find a way to use gconf-editor to rename the share. The information in /desktop/gnome/connected_servers/ is no longer used. I'm using Ubuntu 8.04, Nautilus 2.22.2. P.S. It would have been nice if Nautilus migrated the old connections. Its a good thing I knew to look in gconf to get my connection information.
*** Bug 498383 has been marked as a duplicate of this bug. ***
We no longer show properties dialog for these network items so this is obsolete. There is one case here where we probably want to open a new bug. In the case where you have an existing bookmark for which you can no longer login we should show a "cluebar" that offers to forget the current login information and prompts you for it again. Added bug 682640