Comment 1 for bug 429880
Revision history for this message
| Martin Pitt (pitti) wrote Re: udevadm trigger is not permitted while udev is unconfigured. | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
The main problem here is that the karmic apparmor user space tools don't work on the jaunty kernel, thus AA profile fails to load, and subsequently cupsd fails to start (since it's still running under the old profile).
In order for this to work, we need to special-case the upgrade path to disable apparmor on upgrade until the next reboot. Security team, I expect this will happen with other packages which ship apparmor rules. Is there a general recipe for this already?
As for the "udevadm not permitted", I think we should make cups depend on udev.