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
reassign 632673 gdm3
thanks
On Tue, Jul 05, 2011 at 10:00:01AM +0200, Josselin Mouette wrote:
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
Le mardi 05 juillet 2011 à 01:19 -0700, Steve Langasek a écrit :
*What* bug? libpam0g doesn't invoke /etc/init.d/gdm3, in any version of the
package. It invokes /etc/init.d/gdm only with the 'reload' option, which is
guaranteed by policy not to restart the service. If calling
reassign 632673 libpam0g
found 632673 1.1.3-2
tags 632673 = wheezy sid confirmed
severity 632673 serious
thanks
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
4 matches
Mail list logo
