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
> '/etc/init.d/gdm reload' caused gdm (or gdm3) to die, this is a bug in gdm,
> not in pam.
/etc/init.d/gdm reload will not do anything when gdm3 is started. The
package name is different, the binary name is different.
> 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.
--
.''`. Josselin Mouette
: :' :
`. `'
`-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
