Incorrect access permissions on first autofs connection through Thunar
Submitted by Tony Paulic @ToZ
Assigned to Jannis Pohlmann
Description
When connecting to remote shares (cifs in this case) via autofs, upon first access by Thunar to the share permissions are incorrect (no access to write). If you close Thunar and re-open it, the share access is now correct. Similarily, if you ls the share in a terminal window first then access from Thunar, then it also works properly.
Not fully convinced that its a Thunar issue, but its odd that closing and re-opening thunar causes the permissions to be read correctly.
More info at this forum thread: https://forum.xfce.org/viewtopic.php?pid=33529
Version: 1.6.3
Activity
@ToZsaid:Sorry Harald, but the problem persists even with the latest version of Thunar from git.
I have autofs mounting with the ghost parameter (making directories visible even if not mounted) with this setting: /media/gateway /etc/autofs/auto.gateway --timeout=60 --ghost
It seems, that if the automount happens from within Thunar (e.g. I navigate to the directory), then it seems that although Thunar recognizes that the mount happens and displays both the mount point in the side pane and the files in that directory, it doesn't properly account for the permissions (I don't have access to write to that directory. Restarting Thunar makes it re-analyze the permissions and gets them correct.
If, on the other hand, I automount the directory by cd'ing into it from a terminal window - then open Thunar and navigate there, Thunar properly reads the permissions.
This happens everytime the automount event is initiated by a directory view from within Thunar. I have the timeout set for 60, so after 60 seconds, autofs unmounts. If I navigate there from Thunar again (after the timeout and unmount), the same wrong permissions issue occurs.
-
@ToZsaid:Before mounting, the folder is: dr-xr-xr-x 2 root root 0 May 15 22:29 shared
After mounting, it becomes: drwsrws--- 5 toz toz 0 Sep 2 2014 shared
Manually reloading does not help. Only a close and re-open of Thunar helps. I also have Thunar daemon running: toz 3231 3194 0 May15 tty1 00:00:02 Thunar --sm-client-id 2a0697c84-47b8-4f86-a342-86d1c8276002 --daemon
Note: everything works fine from a terminal window with respect to access rights.
gvfs-info before: display name: shared edit name: shared name: shared type: directory size: 0 uri: file:///media/gateway/shared attributes: standard::type: 2 standard::name: shared standard::display-name: shared standard::edit-name: shared standard::copy-name: shared standard::icon: folder standard::content-type: inode/directory standard::fast-content-type: inode/directory standard::size: 0 standard::allocated-size: 0 standard::symbolic-icon: folder-symbolic, folder etag::value: 1431743394:836660 id::file: l36:9153 id::filesystem: l36 access::can-read: TRUE access::can-write: FALSE access::can-execute: TRUE access::can-delete: FALSE access::can-trash: FALSE access::can-rename: FALSE time::modified: 1431743394 time::modified-usec: 836660 time::access: 1431743413 time::access-usec: 835585 time::changed: 1431743394 time::changed-usec: 836660 unix::device: 36 unix::inode: 9153 unix::mode: 16749 unix::nlink: 2 unix::uid: 0 unix::gid: 0 unix::rdev: 0 unix::block-size: 1024 unix::blocks: 0 owner::user: root owner::user-real: root owner::group: root
gvfs-info after: display name: shared edit name: shared name: shared type: directory size: 0 uri: file:///media/gateway/shared attributes: standard::type: 2 standard::name: shared standard::display-name: shared standard::edit-name: shared standard::copy-name: shared standard::icon: folder standard::content-type: inode/directory standard::fast-content-type: inode/directory standard::size: 0 standard::allocated-size: 0 standard::symbolic-icon: folder-symbolic, folder etag::value: 1409704031:741656 id::file: l38:23600928 id::filesystem: l38 access::can-read: TRUE access::can-write: TRUE access::can-execute: TRUE access::can-delete: FALSE access::can-trash: FALSE access::can-rename: FALSE time::modified: 1409704031 time::modified-usec: 741656 time::access: 1431774565 time::access-usec: 299191 time::changed: 1409704031 time::changed-usec: 741656 unix::device: 38 unix::inode: 23600928 unix::mode: 19960 unix::nlink: 5 unix::uid: 1000 unix::gid: 1000 unix::rdev: 0 unix::block-size: 16384 unix::blocks: 0 unix::is-mountpoint: TRUE owner::user: toz owner::user-real: ToZ owner::group: toz
Note that "access::can-write:" is false before the mount and true after the mount.
-
@ToZsaid:If I leave the original folder open and then open another thunar window, the incorrect permissions remain. It seems that only closing that first window and re-opening thunar fixes the inconsistency.
btw, I'm noticing this behaviour on both Thunar 1.6.6 (Xubuntu 15.04) and Thunar 1.6.8git-1ba30278 (Arch linux - built from git).
I can also "touch test" from a terminal window and the file will be created and Thunar will properly update to display this new file, but the permissions within Thunar don't change.
And this is interesting, while Thunar has the incorrect permissions, if I right-click on a file and go to the Permissions tab, it will show the correct permission (read & write) and when I close this dialog and return to Thunar, Thunar now allows me access (permissions have been corrected / re-read).
added 5. Native Mount label
mentioned in issue #670 (closed)
