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 t
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
I had same thing on Ubuntu 8.10 (noexec flag set when exec is in fstab).
Putting the 'exec' option after the 'user' one seems to fix it. Thanks for the
tip !
--
partitions get mounted with noexec flag against fstab will
https://bugs.launchpad.net/bugs/105723
You received this bug notification be
** Changed in: hal (Ubuntu)
Sourcepackagename: None => hal
--
partitions get mounted with noexec flag against fstab will
https://bugs.launchpad.net/bugs/105723
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
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).
--
partitions get m
>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
