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

[Josselin Mouette]

reassign 632673 libpam0g 1.1.1-6.1
severity 632673 critical
tag 632673 squeeze wheezy sid
thanks

Steve Langasek wrote:
> Not a bug in pam.  We *explicitly* avoid restarting gdm in the libpam 
> postinst, instead calling /etc/init.d/gdm reload because gdm is one of the
> few services that we can get a libpam reload of without having to restart
> the daemon directly.  If '/etc/init.d/gdm reload' is causing gdm3 to
> restart, that's unequivocally a bug in gdm3.

Unfortunately the init script name changed as well as the package name,
and it is called /etc/init.d/gdm3 now.

With gdm3 you shouldn’t have to do anything, anyway. The daemon itself
doesn’t link to libpam, only the slave and session worker do, and they
are restarted every time a login is requested. You can call reload
without harm, but it won’t achieve anything related. 

I’m somehow puzzled I didn’t notice that earlier, and I’m really sorry
to see this bug in squeeze now. 

Setting severity critical since it “breaks unrelated packages”. Not sure
the severity is appropriate but it probably should be fixed in squeeze.

Cheers,
-- 
 .''`.      Josselin Mouette
: :' :
`. `'
  `-