Shutting down GDM takes a long time.

Hi there
do you still this under the beta of Hardy heron?, I've never experience this behavior, at least as you describe, here it just take a couple of seconds. I'm guessing you are logged out or don't have many resource consuming applications running in your session at the moment you try this.

Thanks

Can confirm this issue with up to date Hardy beta. When shutting down my laptop with fresh Hardy install X will be dumped straight away and I am dropped to a terminal for at least 30 seconds until I get a quick barrage of Networkmanager related messages then finally the shutdown splash screen.

Looking in /var/log/syslog I noticed gdm was getting a SIGABRT and you can also see the 30 or so second delay in shutdown:

Mar 28 22:27:28 Putmey init: tty4 main process (4573) killed by TERM signal
Mar 28 22:27:28 Putmey init: tty5 main process (4574) killed by TERM signal
Mar 28 22:27:28 Putmey init: tty2 main process (4578) killed by TERM signal
Mar 28 22:27:28 Putmey init: tty3 main process (4579) killed by TERM signal
Mar 28 22:27:28 Putmey init: tty1 main process (4581) killed by TERM signal
Mar 28 22:27:28 Putmey init: tty6 main process (4582) killed by TERM signal
Mar 28 22:27:28 Putmey gdm[5365]: WARNING: main daemon: Got SIGABRT. Something went very wrong. Going down!
Mar 28 22:27:28 Putmey kernel: [ 323.901684] mtrr: no MTRR for 98000000,2000000 found
Mar 28 22:27:58 Putmey avahi-daemon[5005]: Got SIGTERM, quitting.
Mar 28 22:27:58 Putmey avahi-daemon[5005]: Leaving mDNS multicast group on interface ath0.IPv4 with address 192.168.0.197.
Mar 28 22:28:01 Putmey kernel: [ 337.265407] ip6_tables: (C) 2000-2006 Netfilter Core Team
Mar 28 22:28:02 Putmey exiting on signal 15
Mar 28 22:29:02 Putmey syslogd 1.5.0#1ubuntu1: restart.

Also like the bug reporter if I issue a sudo /etc/init.d/gdm stop it takes a good 30 seconds.
Not sure if useful but I'll attach a log from /var/log/gdm
If you don't think gdm is the cause of this long shutdown issue please let me know and I'll refile elsewhere.

Cheers

Can confirm this issue with up to date Hardy beta. When shutting down my laptop with fresh Hardy install X will be dumped straight away and I am dropped to a terminal for at least 30 seconds until I get a quick barrage of Networkmanager related messages then finally the shutdown splash screen.

Looking in /var/log/syslog I noticed gdm was getting a SIGABRT and you can also see the 30 or so second delay in shutdown:

Mar 28 22:27:28 Putmey init: tty4 main process (4573) killed by TERM signal
Mar 28 22:27:28 Putmey init: tty5 main process (4574) killed by TERM signal
Mar 28 22:27:28 Putmey init: tty2 main process (4578) killed by TERM signal
Mar 28 22:27:28 Putmey init: tty3 main process (4579) killed by TERM signal
Mar 28 22:27:28 Putmey init: tty1 main process (4581) killed by TERM signal
Mar 28 22:27:28 Putmey init: tty6 main process (4582) killed by TERM signal
Mar 28 22:27:28 Putmey gdm[5365]: WARNING: main daemon: Got SIGABRT. Something went very wrong. Going down!
Mar 28 22:27:28 Putmey kernel: [ 323.901684] mtrr: no MTRR for 98000000,2000000 found
Mar 28 22:27:58 Putmey avahi-daemon[5005]: Got SIGTERM, quitting.
Mar 28 22:27:58 Putmey avahi-daemon[5005]: Leaving mDNS multicast group on interface ath0.IPv4 with address 192.168.0.197.
Mar 28 22:28:01 Putmey kernel: [ 337.265407] ip6_tables: (C) 2000-2006 Netfilter Core Team
Mar 28 22:28:02 Putmey exiting on signal 15
Mar 28 22:29:02 Putmey syslogd 1.5.0#1ubuntu1: restart.

Also like the bug reporter if I issue a sudo /etc/init.d/gdm stop it takes a good 30 seconds.
Not sure if useful but I'll attach a log from /var/log/gdm
If you don't think gdm is the cause of this long shutdown issue please let me know and I'll refile elsewhere.

Cheers

I've had the same problem on my box. As a temporary fix, I changed "--retry 30" to "--retry 2" in /etc/init.d/gdm, now there's only a almost unnoticeable pause of two seconds during shutdown.

It still says "gdm[<pid>]: WARNING: main daemon: Got SIGABRT. Something went very wrong. Going down!" in syslog, so it probably isn't the perfect solution.

I'm experiencing exactly the same pattern as described by Dean since I upgraded to the Hardy release.

I've got the same problem here. When I shutdown it takes about 30 seconds to stop GDM.
In the logs I'm also seeing WARNING: main daemon: Got SIGABRT. Something went very wrong. Going down!
and
gdm[5411]: segfault at 0000000c eip b78af7e2 esp bfc7db90 error 6
Though sometimes it shuts down normally without any delay, but about 80% of the time it hangs for 30 seconds.

Hi,

This bug has been logged for Hardy Alpha 5. Can someone confirm if it exists on Hardy final release and probably change the description as well? Why is this bug marked as incomplete when nobody has requested for any specific information?

Thanks.

I am confirming I have the same problem with Hardy final.
Shutdown takes a long time... and when I tried
  # date && /etc/init.d/gdm stop && date
it takes exactly 30 seconds to stop gdm.

I suppose it has been not caused by NM, because I tried uninstall it,
reboot, and the problem is still here.

Can be Incomplete status cleared?
As InsClusoe already noticed, there is no unaswered question.

Happens with hardy final here as well.

Installed Hardy Alpha 5 over Gutsy, it happened then and it still happened after I upgraded to Hardy Final.

I've successfuly used my workaround from above, and haven't seen any bad effects so far.

Confirming on Hardy final.

I cannot confirm this bug on my Hardy installations anymore. It's been fixed what I can see.

I testet both

$ sudo /etc/init.d/?dm stop
and
$ sudo init 1

And the shutdown process takes only 5 - 6 seconds which is normal, OK.

Testet both Ubuntu 8.04 32bits and 64bits installations.
-----------------------

For me, the problem is still here - in Hardy, 32bit
GDM shutdown takes 30 seconds.

I confirm the bug with my Hardy final installation over Gutsy.
GDM shutdown takes about 30 seconds.

The temporary fix from pableu is working for me.

I can confirm the bug with Hardy final, "/etc/init.d/gdm stop" takes pretty much exactly 30 seconds.

Sometimes, however (I am currently not able to reproduce the situation), "/etc/init.d/gdm stop" takes less than 1 second.

the issue could be due to gdm crashing on shutdown, similar issues has been fixed in 2.20.6, could you try again after install the update on bug #229866 when it'll be available?

Sebastien was right, the latest set of updates that came down yesterday did fix the issue for me (gdm 2.20.6-0ubuntu1):

Commit Log for Sat May 17 00:11:25 2008
De volgende pakketten zijn bijgewerkt:
gdm (2.20.5-0ubuntu3) to 2.20.6-0ubuntu1
gtk2-engines-pixbuf (2.12.9-3ubuntu3) to 2.12.9-3ubuntu4
libglib2.0-0 (2.16.3-1) to 2.16.3-1ubuntu1
libgtk2.0-0 (2.12.9-3ubuntu3) to 2.12.9-3ubuntu4
libgtk2.0-bin (2.12.9-3ubuntu3) to 2.12.9-3ubuntu4
libgtk2.0-common (2.12.9-3ubuntu3) to 2.12.9-3ubuntu4
libnautilus-extension1 (1:2.22.2-0ubuntu5) to 1:2.22.2-0ubuntu6
nautilus (1:2.22.2-0ubuntu5) to 1:2.22.2-0ubuntu6
nautilus-data (1:2.22.2-0ubuntu5) to 1:2.22.2-0ubuntu6

It works for me too now, with the updated gdm.

I can confirm the fix.

I have this problem to with gdm 2.20.6. Reinstalling version 2.20.5 solves the problem!!!

I have no more problems with 2.20.6.

the issue seems to be fixed for most people, if somebody still get a bug better to open a new ticket