Package: libpam0g Version: 0.99.7.1-3 Severity: important
Hi, Upgrading libpam0g just killed my X session. It listed 'gdm' among the services to restart, which I accpted since I knew that gdm was safe to restart since gdm postpones the 'restart' action until I log out. But it turns out that libpam0g does _NOT_ use the 'restart' method, but instead tries to do a manual 'stop'/'start' sequence, which is just plain WRONG. Please stop that! Gabor -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22.1 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libpam0g depends on: ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries ii libpam-runtime 0.99.7.1-3 Runtime support for the PAM librar libpam0g recommends no packages. -- debconf information: * libpam0g/restart-services: squid saslauthd postgresql-8.2 gdm cupsys cron atd libpam0g/restart-failed: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
