GNOME Bugzilla – Bug 760881
file can't be saved if executable attribute is not set
Last modified: 2016-01-22 09:47:50 UTC
Following commit caused that it is not possible to save files on e.g. smb, or ftp shares: https://git.gnome.org/browse/gtk+/commit/?id=8e975b28ff460db3bf8ea99f5a07fb9d709c4f1c See Bug 753969 for more details. The problem is that some backends do not set executable attribute at all and thus error is shown instead of choosing the file. It was originally reported downstream: https://bugzilla.redhat.com/show_bug.cgi?id=1204907
Created attachment 319436 [details] [review] file chooser: Allow saving even if executable attribute is not set
Comment on attachment 319436 [details] [review] file chooser: Allow saving even if executable attribute is not set Let's assume that the folder is accessible even if the attribute is not set.
Review of attachment 319436 [details] [review]: ok
Review of attachment 319436 [details] [review]: The patch looks good... even better would be to fix the gvfs backends :)
Comment on attachment 319436 [details] [review] file chooser: Allow saving even if executable attribute is not set Thanks for review! Pushed to master as commit b2eaed6 and gtk-3-18 as commit d5aa2e9 .
I will take a look in gvfs backends, but the problem is that some protocols doesn't provide such info unfortunately, or it is unreliable. We can set can-execute = TRUE for directories even without support of protocols, however it should not be always true...
*** Bug 760975 has been marked as a duplicate of this bug. ***