*** This bug is a duplicate of bug 229270 ***
https://bugs.launchpad.net/bugs/229270
I don't think this is a duplicate. I read the other ticket and the
upstream report on the same. It talks about the gfs not being able to
map remote user and group ids to the local machine. On my nautilus it
correctly shows the remote uid and gid as numbers. The problem being
reported here is that gedit will open a file as read-only unless the
remote user owns the file regardless of who that is and what groups
they're in. I could see how the other problem is related, but the
simple fix for this is to not kick gedit into read-only mode if it's
unsure of the user's write status, but rather find out when the user
tries to write the file.
Not allowing saves when the system is unsure if it can save, is a very
bad default. Many work environments have files owned by several users,
but in a common group that they all have access to. A simple, but
annoying workaround is to use the save as feature and save over the
file, then it's marked as editable.
Please change the default behavior to not assume read-only when that's
not the case. Perhaps a warning that the file may not we writable, or
some easy mechanism to attempt to save even when gedit thinks it's
readonly.
--
Gedit fails saving writable but not-owned files over SFTP
https://bugs.launchpad.net/bugs/284540
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
