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 515906 - Not recogizing ownership on sftp mounts correctly
Not recogizing ownership on sftp mounts correctly
Status: RESOLVED DUPLICATE of bug 531598
Product: nautilus
Classification: Core
Component: [obsolete] GIO
0.x.x [obsolete]
Other Linux
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-12 00:09 UTC by Michael Monreal
Modified: 2008-05-12 22:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22

Attachments
Screenshot (66.88 KB, image/png)
2008-02-12 00:20 UTC, Michael Monreal 		Details

Description Michael Monreal 2008-02-12 00:09:32 UTC 
I connected to my sftp share like this:

sftp://me@my.server.com

After that, I'm unable to modify files by "me", nautilus says I don't have the permission to do it and the controls are grayed out.

Also, when I copy over a file, it is created with just the read flag for the user.

This is a regression introduced after 2.20.
Comment 1 Michael Monreal 2008-02-12 00:20:53 UTC 
Created attachment 105004 [details]
Screenshot

This shows the file permissions window on a file inside my home folder (on the sftp mount). I used to be able to edit those files using nautilus 2.20
Comment 2 Cosimo Cecchi 2008-02-12 09:33:50 UTC 
-> GIO.

Confirming, this is reproducible here.
Comment 3 Michael Monreal 2008-03-03 16:07:19 UTC 
I think this may be the same bug as one I filed in 2006, which was reassigned and fixed in gnome-vfs, see bug 346676.
Comment 4 Sebastien Bacher 2008-05-12 22:10:52 UTC 
that's similar to bug #531598
Comment 5 Cosimo Cecchi 2008-05-12 22:56:53 UTC 
Thanks Sebastien, this should really be the same bug, marking as a duplicate (this one is older, but the other one has much useful comments on it and it is assigned to the correct component).

*** This bug has been marked as a duplicate of 531598 ***