udevadm trigger is not permitted while udev is unconfigured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Karmic |
Fix Released
|
High
|
Martin Pitt | ||
hplip (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Karmic |
Invalid
|
Undecided
|
Unassigned | ||
pxljr (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Karmic |
Invalid
|
Undecided
|
Unassigned | ||
splix (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Karmic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: cups
Upgrading 9.04->9.10 Alpha 5:
Setting up cups (1.4.0-5) ...
Installing new version of config file /etc/cups/
Installing new version of config file /etc/cups/
Installing new version of config file /etc/init.d/cups ...
Installing new version of config file /etc/apparmor.
apparmor_parser: Unable to replace "/usr/lib/
* Starting Common Unix Printing System: cupsd cupsd: Child exited on signal 6!
cupsctl: Unable to connect to server: Connection refused
udevadm trigger is not permitted while udev is unconfigured.
lpinfo: Connection refused
...
Setting up hplip (3.9.8-0ubuntu5) ...
Installing new version of config file /etc/hp/hplip.conf ...
Creating/updating hplip user account...
lpinfo: Connection refused
...
Setting up splix (2.0.0-2ubuntu1) ...
lpinfo: Connection refused
...
Setting up pxljr (1.1-0ubuntu6) ...
lpinfo: Connection refused
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.