Bug#445616: gdm: Problem on reboot

[Daniel Leidert]

Am Freitag, den 04.01.2008, 16:35 +0100 schrieb Josselin Mouette:
> Le lundi 26 novembre 2007 à 17:31 +0000, Daniel Leidert a écrit :
> > Josselin Mouette wrote:
> > 
> > > I have also noticed similar behavior after the upgrade, but it seems
> > > that now the shutdown process is working properly. Could you confirm
> > > whether this is the same for you?
> > 
> > Still the same issue here on a recent Debian Sid. E.g. last night:
> > 
> > > Nov 26 02:11:09 leidi acpid: client connected from 6269[0:0] 
> > > Nov 26 02:11:09 leidi acpid: 1 client rule loaded 
> > > Nov 26 02:11:16 leidi init: Switching to runlevel: 0
> > > Nov 26 02:11:16 leidi gdm[6301]: CRITICAL: gdm_connection_close: assertion `conn != NULL' failed 
> 
> This looks similar to #459024, which additionally shows the slave dying
> in terrible pain. Does it also happen this way with 2.20.2 for you?

The last update "fixed" the issue partially for me (sorry, forgot to
report this). That means, gdm is not restarted, but I can still see some
errors from time to time on my console during reboot/shutdown.

E.g. last night:

> Jan  4 00:59:28 leidi gdm[6135]: CRITICAL: gdm_connection_close: assertion `conn != NULL' failed 
> Jan  4 00:59:28 leidi last message repeated 2 times
> Jan  4 00:59:28 leidi gdm[3449]: WARNING: gdm_cleanup_children: child 6135 crashed of signal 11 
> Jan  4 00:59:28 leidi gdm[3449]: WARNING: gdm_cleanup_children: Slave crashed, killing its children 

So it seems, there is still some issue (maybe the one reported in
#459024 ... didn't read this report yet).

Regards, Daniel