Re: BUG on permission check with ACLs : possible to disable it ?

[António Fernandes <antoniojpfernandes gmail com>]

Sorry for the delayed reply, this got pushed down my email inbox.

Prunk Dump via nautilus-list <nautilus-list gnome org> escreveu no dia segunda, 1/10/2018 às 19:00:

Le lun. 1 oct. 2018 à 17:59, António Fernandes <antoniojpfernandes gmail com> a écrit :

I've not learned about NFS referrals, so I'm not sure if the same logic applies, but it seems wrong that something would be mounted just because you open the parent of the mountpoint.

Is the item count of folders (visible in the "Size" column under list view) enabled for remote locations? (There are controls for this in the Preferences dialog.)

I have tried to disable the « size » column. But the referrals are still mounted while traversing the parent.

I think that is when Nautilus read ACLs.

Can you gave me hints of where to check the code ?

I don't know if the same is true for the source code the debian package builds from, but in the upstream master branch, the context menu actions are in src/nautilus-files-view.c. The "new-folder" action is enabled in nautilus_files_view_supports_creating_files(), which is generally when it's not read-only. https://gitlab.gnome.org/GNOME/nautilus/blob/master/src/nautilus-files-view.c

And this is where it confirms if the file (a directory in this case) is read-only https://gitlab.gnome.org/GNOME/nautilus/blob/master/src/nautilus-file.c#L2589 But the GFileInfo is obtained calling g_file_query_info[_async], which I suppose to happen in src/nautilus-directory-async.c, but from here on it's foggy for me.
 

4) To solve the problem I have three possibilities :
-> I can press F5 inside the "Ressource" folder.
-> If I press F5 before entering the "Ressource" folder the crosses
disappears. And when I enter the "Ressource" folder I can create
directories inside it.
-> If from any manner I go a second time inside the "Parent" folder.
The crosses disappears and I can create directories inside the
"Ressource" folder.

These observations suggest that nautilus keeps outdated metadata about the folder until forced to refresh it.

Do you know a workaround ? An idea of something I can do before the bug was resolved ?

I don't know.
 

I will make a bug report on Debian BTS.

Regards,

Baptiste.

--
nautilus-list mailing list
nautilus-list gnome org
https://mail.gnome.org/mailman/listinfo/nautilus-list