Local executable won't start (64 bits)

[Trenien]

Hi,
I recently updated my system from 32b to 64b and although I am overall satisfied with it, I find myself with a peculiar problem : it isn't possible to start local executables scripts. In all cases (whether with my user account or as root), the system just answers with a "permission denied". Of course, all these scripts have been properly made executable beforehand.

I just don't understand what the problem may be. Would anybody have an idea ?

[doktor5000]

If you don't provide more information, that would prove difficult. Please show the output of ls -la on one of those executables.
Also maybe the output of mount
Otherwise, what do you mean exactly by "executable", a shell script? And how did you upgrade your system from 32bit to 64bit?

[Trenien]

Yes, I am talking about shell scripts, made executable through the command

Code: Select all

chmod +x

As for the system, I was under Mageia 32bits, and I installed (after formating the / partition) Mageia 64bits. Since I had forgotten to check the id numbers for my account and associated group, I didn't directly create these accounts when I installed the system, but realocated the account directory afterwards. To make sure there was no problem, I gave all the files to this user account (as root), using

Code: Select all

chown -R user/user /home/<user directory>

I have a few of these scripts (which all worked properly before. Here is one :

Code: Select all

#/bin/sh
leafpad /home/<user directory>/Documents/Todo.txt


This script's path is

Code: Select all

/home/<user directory>/.Todo

An ls -lah of this script gives :

Code: Select all

-rwxrwxr-x 1 user user 46 juil. 13  2011 .Todo*


I honestly see nothing here that enlightens me as to why even root isn't allowed to execute the script.

[Trenien]

I forgot the output of

Code: Select all

mount

(as root) :

Code: Select all

/dev/sdb1 on / type ext4 (rw,noatime,acl,commit=0)
none on /proc type proc (rw)
/dev/sda3 on /home type ext3 (rw,noexec,nosuid,nodev,noatime,acl,user_xattr,commit=0)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
gvfs-fuse-daemon on /home/<user directory>/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=<user name>)


[doktor5000]

/dev/sda3 on /home type ext3 (rw,noexec,nosuid,nodev,noatime,acl,user_xattr,commit=0)

That's what i was aiming at. This is no default setup, so you put it there during install or afterwards.
It's basically there to disallow execution. As you have added it yourself, you should know what it does.
Remove that option, and either remount /home or reboot, and you should be fine.

For reference, here's a default fstab entry for a /home partition:

Code: Select all

UUID=some-really-long-alphanumeric-UUID /home ext4 acl,noatime 1 2

[Trenien]

Well, thanks for pointing it up, I didn't even think of looking there, but I must say that I didn't add it myself (I never mess with the settings of the root or home partitions).

I suppose it may be a bug of some sort with the installer.