> The one thing I would note is that, in the rare case that there are no > system-level daemons running on your system that use PAM, the message will > not be shown. Michael, before the screensaver locked up on you, did you see > the debconf warning that Christian quotes above?
I do not recall seeing any warnings or dialogs. I followed the instructions (almost) as posted: I changed my sources.list to lenny and installed apt, dpkg, and aptitude. Then I ran "apt-get dist-upgrade" rather than "aptitude upgrade". Then I let the download start and left the computers. When I came back I was unable to log in. > If not, what services do > you have installed on your system? (Even at, cron, cups, gdm, or samba > should trigger display of this message.) And what debconf settings did you > use when running the upgrade? I'm running cups and gdm. I'm not sure what debconf settings I used... I'm guessing I used the defaults? > If this is the cause of the problem, then we could address that by either: > > - having libpam-modules pre-depend on libpam0g (>= 0.99.7.1), forcing the > question to be displayed before libpam-modules is unpacked > > or > > - adding a separate debconf question about screensavers only, shown in the > package preinst advising the user to disable their screen lock for the > duration of the upgrade. As a user, I would prefer the first of the two solutions. As long as I can log in when I come back to the computer and have that dialog waiting, I would be content. Otherwise there are going to be a lot of people (that don't have the patience to read instructions) that will get locked out and be ticked off. This is one of those issues that the reviews will bitch and moan about. If this problem can be dealt with now, before the release, then it should. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
