Stopped on prerm during upgrade, not just remove
Bug #430878 reported by
Anders Kaseorg
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
acpid (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
apport (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
at (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
avahi (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
cron (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
dbus (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
hal (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
ifupdown (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
network-manager (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
util-linux (Ubuntu) |
Fix Released
|
High
|
Scott James Remnant (Canonical) |
Bug Description
Binary package hint: network-manager
Before the upstart transition, network-manager’s prerm would only stop the daemon if the package was being removed. Now, the prerm stops the daemon unconditionally, which means the network is brought down for the entire duration of any upgrade that includes a new network-manager.
This would be fixed by setting DEB_DH_
description: | updated |
Changed in dbus (Ubuntu): | |
status: | New → Invalid |
Changed in util-linux (Ubuntu): | |
assignee: | nobody → Scott James Remnant (scott) |
importance: | Undecided → High |
milestone: | none → ubuntu-9.10-beta |
status: | New → Fix Committed |
To post a comment you must log in.
I filed the transition issue with ‘restart’ failing as bug #430883.