GDM error on shutdown/restart

I also get this problem, but it's only noticeable on shutdown. I'm using Hardy 8.0.4.1 64 bit Ubuntu on a AMD64 PC with nVidia 7600GS display card, Broadcom 4306 wireless. The Glib critical message is the last message that is displayed before the final shutdown message. I can provide further logs and info if required. What's strange is that it seems to have no effect on the system.

Same issue. Ubuntu Hardy 64bit LANG=it_IT.UTF-8
When I shut down the system I get the following error:
gdm[2657]: GLiB-CRITICAL: g_hash_table_lookup_extended: assertion 'hash_table != NULL' failed
gdm[2657]: WARNING: Request for invalid configuration key xdmcp/Enable=false

Thank you for your bug report, the issue is known upstream, you can read about it on http://bugzilla.gnome.org/show_bug.cgi?id=517526

The solution of problem was found by gdm team. Ubuntu users waiting for fix for this bug.

I'm also seeing this bug on my newly installed and updated Ubuntu 8.04.1 system. I never noticed it occurring with the initial release of Ubuntu 8.04.1 It only started showing up after I did a full-upgrade. I'm assuming that this bug didn't exist in the initial hardy 8.04.1 release but was introduced with the gdm update that was applied afterwards. Waiting for a correct fix to propogate to the ubuntu repositories...waiting...waiting... :)

This may or may not be of any help, but I offer it just in case. I just did a clean install of Ubuntu 8.04.1 and then put a hold on the package "gdm" before doing a full-upgrade. Everything was upgraded to the latest packages as of today, Aug. 30, 2008, except "gdm" which was held at the version shipped with 8.04.1

After the upgrade, Ubuntu started displaying the error message described at the top of this thread during system reboot. So, this evidently isn't being caused by upgrading the "gdm" package, but by some other package upgrade.

This bug was fixed in the package gdm - 2.20.8-0ubuntu1

---------------
gdm (2.20.8-0ubuntu1) intrepid; urgency=low

  * New upstream version:
    - Improve gdm_final_cleanup so that the slave daemon exits after receiving
      a shutdown or reboot event, and after completing all cleanup.
      This further fixes bug #517526. which was causing GDM (lp: #249039)
      to crash on reboot or shutdown.
    - Fix broken check in configure for TCP wrappers. Fixes bug #548676.
    - Correct memory leak in SELinux code.
    - Use g_strdup when copying strings in gdmchooser to avoid a crash.
      See bug #544730.
    - Ignore ENXIO when processing ioctl since some distros, such as
      FreeBSD, yields ENXIO for non-IP/non-configured interfaces.
      Fixes bug #544790.
    - Prevent a negative value when processing SVG images in the
      gdmgreeter themes.
    - Add Kazakh language to locale.alias.
    - Translation updates

 -- Sebastien Bacher <email address hidden> Thu, 04 Sep 2008 13:57:09 +0200

Glad to see a fix, but I can't find the gdm 2.20.8-0ubuntu1 package for hardy. How soon will the hardy repository receive the fixed package?

the new version has been uploaded to intrepid, it's not consider for hardy at the moment. the stable update usually need testing to make sure they don't introduce new bug, there is no urgent fix in this one so there is no reason to rush into an hardy update, the warning is cosmetic but might be interesting to fix though

On Fri, 2008-09-05 at 12:39 +0000, Sebastien Bacher wrote:
> the new version has been uploaded to intrepid, it's not consider for
> hardy at the moment. the stable update usually need testing to make sure
> they don't introduce new bug, there is no urgent fix in this one so
> there is no reason to rush into an hardy update, the warning is cosmetic
> but might be interesting to fix though
>
I see. If I'm not misunderstanding you, thought, this fix will be put
into hardy when it is determined to be stable, correct? After all, hardy
is the LTS, and many people and organizations will choose not to upgrade
to intrepid in order to keep their OS an LTS version. Thanks.

the fix is likely to be updated to hardy yes, it's not a priority though since the bug is mainly cosmetic and should be a real issue for users

This bug is not only cosmetic for me! I have regular hangups on shutdown due to gdm crash.
I suppose this fix must be in hardy.

I am sorry, here I am again.
See attached screenshots http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486657#12
Is this cosmetic bug?:-( I have the same problem. Now I want manually install package from intrepid and test.

I am also regularly encountering this bug, and wanted to second Neon Knight's point. Most of the time it simply causes a warning in the system logs, but occasionally (~5% of the time) it causes the entire graphical interface to hang indefinitely. Given that it causes a very common behavior (logging out) to crash with a fairly high frequency, perhaps the importance should be upgraded to "High."

james, the fix to this bug has been released. in fact, i don't get this error any more on intrepid. have you upgraded all your packages to their latest versions? also, in my case it never caused logout to crash

Dimitrios, alas I am running hardy. From the above, it appears that intrepid uses 2.20.8 and has the fix while hardy uses 2.20.7 and retains the bug. But if I am mistaken, please correct me. As for the crashes, the bug appears to result from a race condition in the cleanup, so I expect whether you receive the error message or a crash depends on the precise timing of the logout/shutdown. Neon Knight has also reported that his system will crash upon logout, but I am uncertain as to the exact behavior observed by others who have made comments. Maybe your hardware results in logout that manages to consistently avoid a crash, or maybe my hardware is particularly prone to the crash code path. It might be a different bug, but at this point the error message and the behavior at least seem consistent with this one.

james, thank you for bringing this to our attention
can someone else please confirm that it's not fixed in hardy? hardy is still supported and we should fix it there too!!!

Still seen in Hardy Heron 8.0.4.1. 32 bit latest kernel.

Sorry, just to confirm, I get this problem on my Celeron laptop and see the message, but I don't get any crashes.

To confirm I have the same problem. I see exactly the same message on my HP Laptop. All updates are in place.

It is not a good thing to have when you are demonstrating the virtues of Ubuntu to windows and other users.

I have this problem too. I using ubuntu 8.04.2 64bit on my laptop FSC and I think that this fix packages should be add to hardy repository or to hardy-backports.

I also have the same problem while using Ubuntu 8.04.2 32-bit on a Dell D400 laptop.
Is there an estimate when the fix (using 2.20.8) will appear in the repository?

I also have the same problem using Hardy Heron on 64-bit with Geoforce 9600 GT.

I want to bring to the attention of the package maintainer of gdm in Ubuntu that this bug has yet to be fixed in Ubuntu Hardy 8.04.2 as of Feb. 28, 2009, at least on the i386 version and probably the other platforms. Please don't forget about all of the Hardy users who will be on this version for some time to come. Many, many people don't upgrade with every bright new version. Who want's to be forced to upgrade just to catch bugfixes? It appears that the fix has been made in the upstream version of Ubuntu and Hardy has just been forgotten about.

The fix has not been released for Hardy, therefore this bug is still open as far as Hardy is concerned.

the bug is fixed in the current version so it should be closed, backports tasks can be opened if required

that's only a warning printed for some seconds on restart or stop not sure that's worth a stable update

On Mon, 2009-03-02 at 09:36 +0000, Sebastien Bacher wrote:
> that's only a warning printed for some seconds on restart or stop not
> sure that's worth a stable update

I disagre. GDM is a main Ubuntu package, so it merits that the fix be
applied. From what others have reported, this also affects stability for
at least some users. That in and of itself merits a bugfix be applied to
Hardy. Also, Hardy is supposed to be an LTS release, is it not? That
means it will be around for a minimum of three years for many users,
including corporate users who may be adopting Ubuntu. Does Ubuntu really
want to give its users the impression that it isn't interested in
providing all possible bugfixes for LTS versions even if the fix is
already known?

the ubuntu-desktop is small, made mainly of volunters and working on hundred of packages for several ubuntu version, it's just not possible with those ressources to backport every cosmectic change to stable versions

Just to report that I am also facing this bug AFTER updating Hardy 8.04 to 8.04.2. ( gdm is 2.20.7-0ubuntu1.1).
I haven't had any shutdown problems before updating to latest LTS version.

I'm running ubuntu studio 8.04, and after updates i can see the same error messages. Also my computer won't shutdown. It makes sound like it does, obviously some things turns off, some don't (i guess). So i have to do it manualy with power button. Restart is working fine.

Still present in the second update to Ubuntu 8.04. Ubuntu 8.04.3 will supposedly be released in about a month or two (07/02/2009). This would be a good time to just apply the patch and get this bug fixed in Ubuntu 8.04 LTS once and for all. As users have reported, this isn't just a cosmetic issue for them, it's causing shutdown issues.

Absolutely *not* cosmetic for me. With a freshly updated 8.04, I see this hang on absolutely every shutdown. It is not clear that I can move forward past 8.04 LTS without losing the accelerated nvidia drivers and with that, I would lose a critical application. The primary user of the machine is not in wheel, and therefore will *not* be given 'sudo shutdown'. If further research shows that I can not move forward without losing nvidia capability, then my only rational solution is to scrape Ubuntu off the machine and install a different distro.

For the record... on further investigation, I no longer believe that this bug is the cause of my particular shutdown hang. It *is* the last error message in the shutdown log, but after the message is issued, I hear the hard disk park, and see a "power down" message. My current thinking is that the shutdown hang is an ACPI bug of some flavor, it's just that this gdm assertion failure is the last incriminating evidence and makes gdm look quite guilty.

> With a freshly updated 8.04, I see this hang on absolutely every shutdown.

you are having a different issue then, this bug is about an error displayed not a hang issue