partitions get mounted with noexec flag against fstab will

Bug #105723 reported by Vince on 2007-04-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hal (Ubuntu)

Bug Description

This is probably hal/pmount related, but I'm really not sure.

There seems to be a problem mounting partitions.
my /etc/fstab.conf contains those line
/dev/sda1 /media/hda1 ntfs-3g exec,noauto,defaults,user,uid=vince,locale=en_US.utf8 0 0
/dev/sda3 /media/storage vfat exec,noauto,defaults,user,uid=vince 0 0
AFAIK, the noauto will cause the drives to be mounted when gnome starts so that their icon will appear on the desktop.
mount reports
/dev/sda1 on /media/hda1 type fuseblk (rw,noexec,nosuid,nodev,noatime,allow_other,default_permissions,blksize=4096)
/dev/sda3 on /media/storage type vfat (rw,noexec,nosuid,nodev,uid=1000)
The noexec flag is set while it should be "exec".
I noticed some options in gconf-editor concerning file systems (system/storage/default_options) and there also the exec flag is set.

Pretty much the same thing happens with an external USB drive.
When I plug my external hard drive (ext3 and vfat partitions on it), I get this
/dev/sdb2 on /media/SG-FAT32 type vfat (rw,nosuid,nodev,shortname=mixed,uid=1000,utf8,umask=077)
/dev/sdb1 on /media/SG-EXT3 type ext3 (rw,noexec,nosuid,nodev)
here, suddenly, the vfat one allows exec while the ext3 has noexec.
Here again, it seems simply impossible to set it up so that it has exec.

Step to reproduce:
Problem A :
- Have a vfat partition on a computer
- set the fstab entry to "exec" and "noauto" for the device
- when you enter gnome after bootup, the device will be mounted as noexec

Problem B :
- Have an external drive with an ext3 partition (no references to it in fstab)
- Plug it in
- It gets mounted as noexec

Current solution :
Unmount the device and remount it with noexec. Works but my Grandmother couldn't do it, plus, it's quite annoying to do it at every boot on a laptop for 4 different partitions.

Szabolcs Szakacsits (szaka) wrote :

From ntfs-3g upstream: people keep reporting this problem with mount(8) too and the solution is to put the 'exec' option after the 'user' one. Maybe this helps you too. I don't know if this is by design or a bug in mount(8) but I guess the latter since it keeps confusing people with the unexpected and undesired behaviour.

Vince (v-brz) wrote :

This might solve "Problem A" (at a first glance, it really seems to solve it, I'll confirm next time I boot).

it still doens't solve "problem B" though (which doens't seem to be a mount related problem but rather a lack of configuration capability for removable ext3 storage).

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in hal (Ubuntu):
status: New → Incomplete

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in hal (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers