upgrade of 'libpam0g' blocks requesting user-input
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pam (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Upgrade from within update-manager blocks awaiting input; copy and paste of terminal window below.
Preparing to replace libpam0g 0.79-4ubuntu2 (using .../libpam0g_
Unpacking replacement libpam0g ...
Setting up libpam0g (0.99.7.1-4ubuntu3) ...
debconf: Unable to initialise frontend: Dialog
debconf: (Dialogue frontend will not work on a dumb terminal, an Emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
Checking for services that may need to be restarted.
Configuring libpam0g
-------
Most services that use PAM need to be restarted to use modules built for this
new version of libpam. Please review the following space-separated list of
init.d scripts for services to be restarted now, and correct it if needed.
Among the services that require restarting are the display managers kdm, wdm,
and xdm. If you are upgrading from within an X session started with one of
these display managers, restarting that service will terminate your X session.
It is recommended that you remove that service from the list here and restart it
later at your convenience.
Some other services such as xscreensaver, gnome-screensaver, and xlockmore
cannot be restarted for you. You will not be able to authenticate to these
services until you restart them manually.
Services to restart for PAM library upgrade:
------------
Ideally this should be a debconf question with a priority such that it doesn't get seen.
| Jorge Juan (jjchico) wrote | #1 |
This bug is a duplicate of #139065.
I can confirm both. In my case, I removed gdm from the list of services to be restarted and the upgrade continued. It will not be obvious for unexperienced users.