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 > > 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. Good to know; I won't add gdm3 to the maintainer script then. > I’m somehow puzzled I didn’t notice that earlier, and I’m really sorry > to see this bug in squeeze now. *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 '/etc/init.d/gdm reload' caused gdm (or gdm3) to die, this is a bug in gdm, not in pam. > Setting severity critical since it “breaks unrelated packages”. Nonsense. If there's a bug here at all, it's not in pam. -- 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/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
