Don't stop the upgrade to inform about service restarts
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pam (Ubuntu) |
New
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: update-manager
The pam upgrade blocks the entire release upgrade process until it is acknowledged:
Preparing to replace libpam0g 1.1.0-2ubuntu1 (using .../libpam0g_
Unpacking replacement libpam0g ...
Setting up libpam0g (1.1.1-2ubuntu1) ...
Checking for services that may need to be restarted.
Restarting services possibly affected by the upgrade:
saslauthd: stopping.
cron: stopping.
atd: stopping.
Services restarted successfully.
While this is normally a good practice, when upgrading to a new release, it risks hanging the upgrade process and serves no purpose (there is no option other than go ahead and all services get restarted at some point during the upgrade process, so this isn't news). This should be notification should be disabled during upgrades to a new release.
| tags: | added: iso-testing |
| Steve Langasek (vorlon) wrote | #1 |
| affects: | update-manager (Ubuntu) → pam (Ubuntu) |
| Changed in pam (Ubuntu): | |
| status: | New → Won't Fix |
| Scott Kitterman (kitterman) wrote Re: [Bug 558440] Re: Don't stop the upgrade to inform about service restarts | #2 |
| Steve Langasek (vorlon) wrote | #3 |
| Changed in pam (Ubuntu): | |
| status: | Won't Fix → New |
| Changed in pam (Ubuntu): | |
| importance: | Undecided → Low |
libpam0g prompts for this on upgrade because it has no way of knowing whether all of those services are being upgraded at the same time. If they're not, the user may not be expecting the service interruption, so the behavior is to ask the user first before restarting services from other packages.
Note that the prompt is suppressed if running under update-manager and the user does not have any non-default services installed. In this case you have sasl2-bin installed, which is not a service installed on a default desktop.