Note that this: Jul 17 03:59:55 utah-11601-saucy-server-i386 kernel: [ 13.514969] type=1400 audit(1374047995.545:11): apparmor="DENIED" operation="file_mmap" parent=488 profile="/sbin/dhclient" name="/bin/bash" pid=591 comm="dhclient-script" requested_mask="m" denied_mask="m" fsuid=0 ouid=0
is a different denial than in bug #1197484. Bug #1197484 denied 'r' access, this is denying 'm' access. Can you boot/test with apparmor=0 to take apparmor completely out of the equation?
Note that this: saucy-server- i386 kernel: [ 13.514969] type=1400 audit(137404799 5.545:11) : apparmor="DENIED" operation= "file_mmap" parent=488 profile= "/sbin/ dhclient" name="/bin/bash" pid=591 comm="dhclient- script" requested_mask="m" denied_mask="m" fsuid=0 ouid=0
Jul 17 03:59:55 utah-11601-
is a different denial than in bug #1197484. Bug #1197484 denied 'r' access, this is denying 'm' access. Can you boot/test with apparmor=0 to take apparmor completely out of the equation?