No executables on ext4 volumes could be run, permission denied
Tofloor
poster avatar
iblis
deepin
2019-01-11 03:38
Author
Edited by androidbrain at 2019-1-10 20:40

Hello guys, after installing this update on 10 Jan 2019, none of my executable files on ext4 volumes could be run. Every time I try to run it, I always encounter "permission denied" error even if the permission of those files were actually set to 777. Those executables on FAT32 or NTFS drives remain unaffected and work properly.
Reply Favorite View the author
All Replies
oscararg
deepin
2019-01-11 09:34
#1
Edited by oscararg at 2019-1-10 17:09

Solved, download Disks utility from Deepin Store, select the disk in which you cannot run executables, mounting options, and add exec after a comma at the end of the line.


Reply View the author
dance707
deepin
2019-01-11 09:49
#2
Take a look at your mount method, and order of mount options. One common reason is being mounted as noexec,  From the man page mount
FILESYSTEM-INDEPENDENT MOUNT OPTIONS
       exec   Permit execution of binaries
       noexec Do not permit direct execution of any binaries on the mounted filesystem.
Reply View the author
oscararg
deepin
2019-01-11 12:01
#3
https://bbs.deepin.org/post/173529
Take a look at your mount method, and order of mount options. One common reason is being mounted as  ...

Thanks for the info, it helped.
Reply View the author
iblis
deepin
2019-01-11 16:41
#4
https://bbs.deepin.org/post/173529
Take a look at your mount method, and order of mount options. One common reason is being mounted as  ...

Well, thanks for your attention, this actually works for now, but every time I use removable disks I have to mount them manually though. It seems that deepin has enhanced its permission management scheme, so I hope that the developers would develop a configuration tool that enables us to set what the system should do with auto mount. https://bbs.deepin.org/user/101846
Reply View the author
oscararg
deepin
2019-01-11 17:13
#5
https://bbs.deepin.org/post/173529
Well, thanks for your attention, this actually works for now, but every time I use removable disks ...

Solved that too, at the same configuration part of "Disks" app change the "mount point" for the same one you had before the update, probably "/media/user/disk-label". And if you have the type of filesystem in auto like I had, change it for the disk's format.
Reply View the author