First! Executable issue when creating file through GUI

[davidpbrown]

Linux Mint 19.3
fuse 2.9.7-1ubuntu1
umask 0022

Through Caja GUI file manager, right click create new document - which is an empty plain text file, normally is just that but in the fuse sn_fs provides it becomes executable looking for when user tries to open it. The flag is not apparent in the properties, which is odd.. and that includes command line as ls -al

It's not a simple Caja bug .. so, on the normal file system it just works as expected creating a normal text file that opens. Potentially is a complex issue, as the executable flag is not showing.

Step 0

Step 1

Step 2

[davidpbrown]

Noting that odd behaviour follows also a simple copy from an environment where the file is not executable.. but only in the GUI not in the command line!

So, a file that is not executable, copied from another normal drive, either through GUI or as command line cp, sees the file immediately present to the Caja[right-click]=>[Open] as if executable.

However, the command line looks ok.

So, this is as expected without a exec flag, it is just denied.

$ echo "echo 'hello Safe Network'" > sayhello.sh
$ cp ./sayhello.sh /media/safe/test/
$ /media/safe/test/sayhello.sh 
bash: /media/safe/test/sayhello.sh: Permission denied

How Caja is not seeing the same permission is a wonder.. could it be that it is a null instead of a zero or sum such.. the exec is not set and therefore behaviour is like a transfer from FAT etc where there is no flag?