Comment 18 for bug 581525

Revision history for this message
Seth Arnold (seth-arnold) wrote :

John, thanks for this updated kernel; I received 39 or so "AppArmor DFA next/check upper bounds error fixed, upgrade user space tools" per /etc/init.d/apparmor reload command.

I was able to re-install my /home/sarnold/Local/io/** profile with no obvious problems: both the Io interpreter appears to run fine and grotty was _not_ mistakenly attached. :) So great success there.

I also put my /etc/init.d/origami profile back in place and continued development of the profile. (This made my machine very unstable before; no system stability issues yet. Good work.)

I'm getting some very funny errors though:

5013 execve("/bin/bash", ["sh", "-", "/bin/bash", "-c", "/bin/bash -c \"cd /var/lib/origam"...], [/* 12 vars */]) = -1 ENOENT (No such file or directory)

This error is _not_ accompanied by any AppArmor log messages. It is a silent fail. Removing the AppArmor profile allows origami to start as normal.

I'll attach my /etc/init.d/origami profile, maybe it'll be obvious to you.