Well, the update should have triggered an apparmor profile reload,
though maybe there was a race condition there or just a bug in apparmor
that made the reload fail somehow.
Anyway, I'm glad that you both confirmed that the latest package indeed
fixes the regression I introduced with the previous
Latest package update fixed it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172148
Title:
isc-dhcp-server didn't restart after upgrade
To manage notifications about this bug go to:
https://bugs.l
I can confirm the md5sum. Doing a simple service start from a terminal
session was also possible/enough without apparmor complaining, so I
already had the dhcpd running again.
I guess reloading apparmor needs to be ensured on package updates, then?
--
You received this bug notification because y
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: isc-dhcp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172148
Title:
i
Can you confirm that the md5sum of /etc/apparmor.d/usr.sbin.dhcpd is
c4a3f842da64006353d11d907b8b1752?
If it's, then try:
- sudo /etc/init.d/apparmor reload
- start isc-dhcp-server
The bug you're describing above is exactly the same as was introduced in
4.2.4-1ubuntu10.2 and then fixed in 4.2.4
