cannot execute programs/scripts from USB drives (including reiserfs and ext)

I'm having the same issue do you know of a fix?

I can confirm that. Since a while (maybe feisty) I can't run bash script on my external USB Harddrive.

This is the opposite bug to #60722. Since USB drives that must interface with Windows are formatted with FAT, they lose all permission data, including the executable permission. Hence, when a FAT drive is mounted, either all the files must be marked as executable, or none. If they are all marked as executable, Nautilus will ask the user whether to "Open" or "Execute" the file when double-clicked, which is irritating and confusing for new users.

I understand that this may not be an issue in KDE, but whatever change is made will affect both desktops.

As I see it, it makes more sense to leave everything marked as non-executable and risk annoying advanced users (presumably, you can execute it using sh from the command line) rather than confusing new users.

I don't know about FAT drives but I see no reason ext3 formated drives shouldn't have the execute bit work correctly which currently it doesn't.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nor does reiserfs start as executable. I also understand the vfat issue,
and I agree. But ext2/3/4, xfs, reiserfs 3/4 should be executable IMHO.

- -Dave

Spencer wrote:
> I don't know about FAT drives but I see no reason ext3 formated drives
> shouldn't have the execute bit work correctly which currently it
> doesn't.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGX2mEwapA6Qc539wRAqfDAJ90uf7rTG9Pz8o2rB/J20T8lbsb+QCeN4JK
RTfnSmLQfqXVAvpfZCi9VHc=
=yUC+
-----END PGP SIGNATURE-----

I agree -- filesystems that support the execute bit should work, which is a bug. I did not realize you were talking about non-FAT drives... perhaps you could add reiserfs or ext to the bug description so this is clearer?

Closing kubuntu-meta, this isn't a kubuntu-meta issue. I have multiple ext3 usb sticks and my 500gb drive is external usb that I can execute and do whatever from, so I cannot confirm, however I will confirm due to the responses, I just need to find out what would be the problem behind this.

I am assigning this to pmount as the issues everyone here is reporting seems to be with external/usb devices in which pmount wraps around the standard mount app for devices without matchind /etc/fstab entries.

I apologize if this is the incorrect package, but the *-meta packages I felt were incorrect as I am able to do what they are saying they can't w/o any issues.

I dont know how you are mounting exactly your drives, but if you use pmount directly, you might be interested in the -e option, that does exactly this, such as in, say,

pmount -e /dev/sda1 my_nice_drive_label

I don't know if that would be a good idea to systematically change the default behaviour.

The -e option along with -fmask 055 worked. Although every file is mounted as executable.
pmount by default was using file_umask=0111.