Morten Kjeldgaard wrote: > That's what I would have done, but SELINUX does not appear to be enabled > on Ubuntu's kernel: > > $ grep SELINUX /boot/config-2.6.28-11-generic > CONFIG_SECURITY_SELINUX=y > CONFIG_SECURITY_SELINUX_AVC_STATS=y > CONFIG_SECURITY_SELINUX_BOOTPARAM=y > CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0 > CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1 > CONFIG_SECURITY_SELINUX_DEVELOP=y > CONFIG_SECURITY_SELINUX_DISABLE=y > # CONFIG_SECURITY_SELINUX_ENABLE_SECMARK_DEFAULT is not set > # CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set > > The /selinux directory exists, but is empty. > > try (as root) echo 0 >/proc/sys/kernel/exec-shield echo 0 >/proc/sys/kernel/randomize_va_space
If that cures the problem then the problem is SELinux If not, then I'm completely puzzled because the error you report has always been caused by SELinux. See faq 36 and faq 37 Tim -- axiom version 20081101 FTBFS on all platforms https://bugs.launchpad.net/bugs/387255 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
