GNOME Bugzilla – Bug 169726
Connect to sever (SSH) file permissions are wrong (cannot save files)
Last modified: 2005-05-09 19:46:04 UTC
Distribution/Version: Ubuntu Hoary For this example: Local user = USER1 Remote server user = USER2 1. Menu - Places - connect to server -> create SSH connection to server, with an existing user name on this server (USER2). 2. Open a directory on the server -> check files owner/group -> owner/group is USER1 (the local user), but it should be USER2 ! 3. Try to open a text file -> it opens in gedit -> but I cannot save it ! (because file permissions are wrong). This is working fine in KDE (I can open files and save them -> permissions are right (owner/group is always the user on the remote server). Please fix this, it is a very important feature for me, I use it every day. Many thanks.
Are you *sure* it's because of file permissions you can't save to the remote location ? gedit can't directly save to remote locations, they are always set to read-only. A better test would be to try to copy a file to the remote location using nautilus.
Yes I can copy a file to the directory. But if I check the files permissions, it shows everything is owned by the local user (not the remote user, which I used to login to the server). I am pretty sure that I remeber that in KDE this was displayed right (showing the real ownership of the files). And yes, as you say it seems the file is read only, without any way to select the remote location in the save dialog. This is a problem. In KDE it works well. Please fix this, so that we can work on a remote server in the same way we can in KDE (open a file - edit it - and save it back).
« And yes, as you say it seems the file is read only, without any way to select the remote location in the save dialog. » This is a known problem with gedit, but it's not really easy to fix that's bug 110191 « But if I check the files permissions, it shows everything is owned by the local user (not the remote user, which I used to login to the server). I am pretty sure that I remeber that in KDE this was displayed right (showing the real ownership of the files). » It's indeed not totally nice, but it's cosmetic only, so not that important ;)
Thanks for your replies. > This is a known problem with gedit, but it's not really easy to fix that's > bug 110191 Ok, as per this bug's comments, it's about to be worked on... great. Does this mean that this problem only exists with gedit (works with other applications) ? > « But if I check the files permissions, it > shows everything is owned by the local user (not the remote user, which I >used to login to the server). I am pretty sure that I remeber that in KDE >this was displayed right (showing the real ownership of the files). » > > It's indeed not totally nice, but it's cosmetic only, so not that >important ;) Well.... there are quite many problems with the file permissions dialog: 1. Setting permissions on remote files (as above) does not work. 2. Setting permissions recursively on a local directory does not work (if I want to change permissions on all the files in a dir and its subfolders, I have to do it manually for each file, this is unusable -> need the shell to achieve this) 3. Changing the group of several files at once is not possible (by selecting several files) All this has been working perfectly with KDE for a long time, but in Gnome it is not possible to do.
Thanks for your bug report! 2., 3. are nautilus issues. IMHO, there are separate bug reports open. 1. is a duplicate of bug 155866. We're not quiet there yet, but working on it [don't hold your breath] :). *** This bug has been marked as a duplicate of 155866 ***