Bug#632673: Processed: Re: Bug#632673: libpam0g: Kills gdm3 when upgrading package

Steve Langasek vorlon at debian.org
Tue Jul 5 16:03:50 UTC 2011

reassign 632673 libpam0g
found 632673 1.1.3-2
tags 632673 = wheezy sid confirmed 
severity 632673 serious

On Tue, Jul 05, 2011 at 10:43:14AM +0200, Josselin Mouette wrote:

> > Nonsense.  If there's a bug here at all, it's not in pam.

> It’s a pam upgrade which (supposedly) triggered the problem, not a gdm
> one. There is nothing that will ever stop or restart gdm3 in its
> maintainer scripts, since it’s not possible.

> Tag the bug unreproducible if you want, but there is nothing in gdm3
> that will make it restart.

> Other possible explanations: 
>       * the reporter is not actually using gdm3 but something else (the
>         original report lists kdm in restart-services, not gdm); 
>       * something else in the upgrade (hey, hey, dbus) killed the
>         session manager and the reporter thought it had killed the
>         display manager.

Following discussion on IRC, I've noticed that indeed, the original bug
report includes debconf information showing that the user has kdm installed,
not gdm (of any vintage).  So yes, this is a bug in pam, which needs to stop
restarting kdm; that's a recent behavior change in kdm upstream which needs
to be accounted for in the maintainer script.

Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20110705/0ad6416f/attachment.pgp>

More information about the pkg-gnome-maintainers mailing list