Bug ID | 1206199 |
---|---|
Summary | udisks2 ignores fstab mount options and uses the defaults instead |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | x86-64 |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | MicroOS |
Assignee | kubic-bugs@opensuse.org |
Reporter | alexviralata@posteo.org |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:107.0) Gecko/20100101 Firefox/107.0 Build Identifier: I used KDE Partition Manager to configure fstab to automount all of my drives. I activated the users option, and added "exec" as a mount option. The "exec" option isn't working. After some discution on reddit, I found out that udisksctl is in fact reading the fstab file, but the actual mount option used are the "safe defaults", I found this by using "findmnt". Reproducible: Always Steps to Reproduce: 1.Configure fstab to automount any other drive with "exec" mount option 2.Restart computer 3.Try to execute anything on that drive Actual Results: Nothing, since the drive is mount with "safe defaults" and that includes "rw,nosuid,nodev,noexec,relatime,lazytime,etc..." Expected Results: To be able to execute programs inside my drives. All my drives have my user name as owner and group owner. I think that's the only reason why they do actually automount, but with the wrong flags. Once I have fstab configured the way I like, and I unmount and re-mount my drives with KDE Partition Manager, the fstab mount option do get used, among the "safe defaults". SELinux disabled/permissive made no change.