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 703291 - Image can't be saved if G_FILE_ATTRIBUTE_ACCESS_CAN_WRITE isn't set
Image can't be saved if G_FILE_ATTRIBUTE_ACCESS_CAN_WRITE isn't set
Status: RESOLVED OBSOLETE
Product: eog
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-06-28 20:10 UTC by mike
Modified: 2021-06-19 08:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description mike 2013-06-28 20:10:31 UTC
Description:	Ubuntu 13.04
Release:	13.04

nautilus:
  Installed: 1:3.6.3-0ubuntu16
  Candidate: 1:3.6.3-0ubuntu16
  Version table:
 *** 1:3.6.3-0ubuntu16 0
        500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status

Mounting a samba share via gvfs (files > navigating to the server and authenticating) displays the files. Right-clicking on any file and clicking the permissions tab gives "The permissions of <file> cannot be determined."

The properties display correctly from the command line:

mike@mike-Latitude-E6510:/run/user/mike/gvfs/smb-share:server=ulysses,share=mike/comics$ ls -l babies.jpg
-rwx------ 1 mike mike 72238 Apr 21 10:09 babies.jpg

I can verify read/write by opening the file (reading) and deleting it (writing) or even overwriting it, but the following fails:

* Open the image using Image Viewer
* Rotate it
* Click Image > Save

"Could not save image 'babies.jpg'. You do not have the permissions necessary to save the file."

Link to Ubuntu Launchpad Bug report: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1195530
Comment 1 Ηλίας Ηλιάδης 2013-10-17 10:08:39 UTC
I just want to confirm that samba shares (on other computers) "exposed" as windows shares, are not "understood" by nautilus (at least in my ubuntu 12.04 amd64 aka: 3.2.0-54-generic #82-Ubuntu SMP Tue Sep 10 20:08:42 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux), and all give "The permissions of <file> cannot be determined." 

(This also means we cannot see or change the read-only property of a file. The after effect of this, is that nautilus can ex. copy the file, but when it tries to delete it an error is reported by the server that has the share so "moving" is not working.)

But this probably is gvfs-fuse-daemon bug which mounts win32 shares as "linux-like" shares.
Comment 2 Cosimo Cecchi 2014-09-13 05:44:04 UTC
-> gvfs

Yeah, this sounds like a gvfs bug in the Samba backend, if it's still reproducible with latest gvfs.
Comment 3 Ondrej Holy 2014-09-15 13:18:24 UTC
(In reply to comment #0)
> Mounting a samba share via gvfs (files > navigating to the server and
> authenticating) displays the files. Right-clicking on any file and clicking the
> permissions tab gives "The permissions of <file> cannot be determined."

It is because smb backend doesn't support permissions, because we can't get them reliably, see similar bugs for more info: Bug 581368, Bug 569395 and Bug 592651.

> or even overwriting it, but the following fails:
> 
> * Open the image using Image Viewer
> * Rotate it
> * Click Image > Save
> 
> "Could not save image 'babies.jpg'. You do not have the permissions necessary
> to save the file."

Image viewer should try to save the file if g_file_info_has_attribute (info, G_FILE_ATTRIBUTE_ACCESS_CAN_WRITE) is FALSE. So changing component to eog.
Comment 4 André Klapper 2021-06-19 08:47:24 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/eog/-/issues/

Thank you for your understanding and your help.