GNOME Bugzilla – Bug 360400
Owner/group of file lost when saving remotely
Last modified: 2020-11-24 09:59:31 UTC
When I save a remote file the ownership of the file changes to the user and the primary group (tested with saving over ssh). So say I have a file: jesse:members groupfile When I save it, it's: jesse:jesse groupfile
mmm... I know I told you to file this, but I am not sure anymore it is a bug. How can we know if the group exist on both the local and remote machine?
Why do you need it to exist on both remote and local systems? I understand the problem (I think), since we essentially copy a file which overwrites the previous file (thus losing the uid/gid information). The user won't always have permission to restore the uid/gid of the file. I do think this is an annoying bug though. Editing a remote file and having to restore the group everytime I save the file renders the remote editing practically useless. Can't we at least try to restore the group/user (does gvfs even allow this?)
*** Bug 372865 has been marked as a duplicate of this bug. ***
I can confirm this as an issue in gvfs. It effects gedit, kate, nano, etc. equally. It is not preset with sshfs.
Mass-closing of all gedit bugzilla tickets. Special "code" to find again all those gedit bugzilla tickets that were open before the mass-closing: 2bfe1b0590a78457e1f1a6a90fb975f5878cb60064ccfe1d7db76ca0da52f0f3 By searching the above sha256sum in bugzilla, the gedit contributors can find again the tickets. We may be interested to do so when we work on a specific area of the code, to at least know the known problems and possible enhancements. We do this mass-closing because bugzilla.gnome.org is being replaced by gitlab.gnome.org.