apparmor profile for dhcp3-client is too strict

on a up to date maverick AMD64 install, dhclient stopped working: I didn't touch apparmor or dhclient configuration and it worked well 2 days ago. The process get killed as shown by strace:

execve("/sbin/dhclient", ["dhclient", "eth0"], [/* 21 vars */]) = 0
brk(0) = 0x7fd0c8571000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fd0c7e21000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY <unfinished ...>

stopping apparmor allows dhclient to work again, so I guess the problem comes from the apparmor profile included in the package. Unfortunatly, I can't check it as it now fails to fail. I started apparmor again and dhclient works. the strace file starts with the same access and now opening /etc/ld.so.cache works!

execve("/sbin/dhclient", ["dhclient", "eth0"], [/* 21 vars */]) = 0
brk(0) = 0x7fd16bbfd000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fd169f26000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=130154, ...}) = 0
mmap(NULL, 130154, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fd169f06000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)

can anyone reproduce it?

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: dhcp3-client 3.1.3-2ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-8.13-generic 2.6.35-rc5
Uname: Linux 2.6.35-8-generic x86_64
Architecture: amd64
Date: Fri Jul 16 09:52:41 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: dhcp3