GNOME session hangs after login

[Thayer Williams]

GNOME hangs when I log into my desktop. I see a brown background and a grey box in the upper left corner. If I leave it alone for about 8 minutes, it finally loads, with a crash message:

------
There was an error starting the GNOME Settings Daemon.

The last error message was:

Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

GNOME will still try to restart the Settings Daemon next time you log in.
------

I googled a bit and found a thread relating to ESD. Following the thread, I checked my ~/.xsession-errors log and found the following messages, but I can't tell if the reference to ESD is an error or just standard procedure:

------

/etc/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "thayer"
/etc/gdm/Xsession: Beginning session setup...
SESSION_MANAGER=local/dublin:/tmp/.ICE-unix/6081
esd: Esound sound daemon already running or stale UNIX socket
/tmp/.esd-1000/socket
This socket already exists indicating esd is already running.
Exiting...

(process:6180): Gnome-CRITICAL **: gnome_program_module_register: assertion `module_info' failed
Initializing gnome-mount extension
evolution-alarm-notify-Message: Setting timeout for 21451 1172793600 1172772149
evolution-alarm-notify-Message: Thu Mar 1 16:00:00 2007

evolution-alarm-notify-Message: Thu Mar 1 10:02:29 2007

(gnome-panel:6154): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
------

ProblemType: Bug
Date: Thu Mar 1 10:18:55 2007
DistroRelease: Ubuntu 7.04
Uname: Linux dublin 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux

[David Meier (droebbel-melta)]

ESD seems to cause the problem.
Deactivating it in the audio preferences makes GNOME start normally. Reactivating it makes GNOME stop reacting for some minutes. After that the error message about the esound-socket reappears in .xsession-errors.

[demongloom (dima-snaiper)]

I am get same error. Disabling ESD is not helps me.

[demongloom (dima-snaiper)]

Upd: My log
/etc/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "dima"
/etc/gdm/Xsession: Beginning session setup...
SESSION_MANAGER=local/demongloom:/tmp/.ICE-unix/10964
Initializing nautilus-open-terminal extension
Initializing gnome-mount extension

(process:11085): Gnome-CRITICAL **: gnome_program_module_register: assertion `module_info' failed
seahorse nautilus module initialized
*** glibc detected *** x-session-manager: malloc(): memory corruption: 0x08198cf0 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6[0xb763fef3]
/lib/tls/i686/cmov/libc.so.6(__libc_malloc+0x7e)[0xb764160e]
/usr/lib/libglib-2.0.so.0(g_malloc+0x36)[0xb77572c6]
/usr/lib/libgdk-x11-2.0.so.0[0xb7aecdb0]
/usr/lib/libgdk-x11-2.0.so.0(gdk_region_intersect+0x99)[0xb7aee1e9]
/usr/lib/libgdk-x11-2.0.so.0(gdk_window_invalidate_maybe_recurse+0x10d)[0xb7af1f2d]
/usr/lib/libgdk-x11-2.0.so.0(gdk_window_invalidate_region+0x40)[0xb7af21c0]
/usr/lib/libgdk-x11-2.0.so.0(gdk_window_invalidate_rect+0xaf)[0xb7af227f]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_queue_draw_area+0x150)[0xb7da7440]
x-session-manager[0x805ce05]
/usr/lib/libglib-2.0.so.0[0xb77503c6]
/usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x182)[0xb774fdf2]
/usr/lib/libglib-2.0.so.0[0xb7752dcf]
/usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x65)[0xb7753335]
x-session-manager[0x8055789]
/usr/lib/libglib-2.0.so.0[0xb777940d]
/usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x182)[0xb774fdf2]
/usr/lib/libglib-2.0.so.0[0xb7752dcf]
/usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1a9)[0xb7753179]
/usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xb4)[0xb7c87044]
x-session-manager(main+0x5de)[0x805638e]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc)[0xb75edebc]
x-session-manager[0x8051d51]
======= Memory map: ========
08048000-08068000 r-xp 00000000 08:02 43008 /usr/bin/gnome-session
08068000-08069000 rw-p 00020000 08:02 43008 /usr/bin/gnome-session
08069000-081c8000 rw-p 08069000 00:00 0 [heap]
b5700000-b5721000 rw-p b5700000 00:00 0
b5721000-b5800000 ---p b5721000 00:00 0
b585f000-b586a000 r-xp 00000000 08:02 11544 /lib/libgcc_s.so.1
b586a000-b586b000 rw-p 0000a000 08:02 11544 /lib/libgcc_s.so.1
b5879000-b587a000 ---p b5879000 00:00 0
b587a000-b607a000 rw-p b587a000 00:00 0
b607a000-b608b000 r--p 00000000 08:02 86857 /usr/share/fonts/truetype/ttf-bitstream-vera/Vera.ttf
b608b000-b608d000 r-xp 00000000 08:02 42301 /usr/lib/pango/1.6.0/modules/pango-basic-fc.so
b608d000-b608e000 rw-p 00001000 08:02 42301 /usr/lib/pango/1.6.0/modules/pango-basic-fc.so
b608e000-b6091000 r--s 00000000 08:02 111936 /var/cache/fontconfig/5e10083637a12ecd1bff191eb66bfa2f-x86.cache-2
b6091000-b6097000 r--s 00000000 08:02 111877 /var/cache/fontconfig/945677eb7aeaf62f1d50efc3fb3ec7d8-x86.cache-2
b6097000-b609c000 r--s 00000000 08:02 111870 /var/cache/fontconfig/bddabcf04192498a6a74911686fc6962-x86.cache-2
b609c000-b609f000 r--s 00000000 08:02 111851 /var/cache/fontconfig/a46337af8a0b4c9b317ad981ec3bdf87-x86.cache-2
b609...

[David Meier (droebbel-melta)]

demongloom, your problem is obviously different, as the error messages clearly show. You may want to file a separate bug.

[D B (eburner)]

Please see my comment here: https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/91834

Related bugs:
 *https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/91834
 *https://bugs.launchpad.net/ubuntu/+source/gtk-qt-engine/+bug/83152
 *https://bugs.launchpad.net/ubuntu/+source/gtk-qt-engine/+bug/66124
 *https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381
 *https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/84876

[D B (eburner)]

Here's the real culprit.
 *ping localhost

This command wasn't working. Seems when I upgraded to Feisty and when I was setting a static IP, I commented EVERYTHING in /etc/network/interfaces. This is not good as the 'lo' or loopback device is needed. I uncommented auto lo and the iface line for lo, ran ;sudo ifup lo', and I was back with a fast Gnome and no gray screen in the corner.

Hope this helps some of you out there. Thanks to seb for the tip.

[Yuji (yhenry)]

Just like DerekBuranen, on my system I had the same issue when logging in a grey box appeared, relogged in with failsafe GNOME and actually got it to boot once, and it showed the error listed at the top. Well checking my etc/network/interfaces file and of course i had to do some commeting items out and low and behold I commented out the:

auto lo
iface lo inet loopback

But once I allowed the system to see the loopback the desktop loaded without issue. So I dont believe it to be a sound issue and or a bug.

Thanks Derek for the info.

[Monteaup (m-cz)]

I think I got the solution. It has something to do with the repository. I got the error with "...can't be authenticated..." on reinstalling the ESD packages. So I changed the Repository to the original one and reinstalled the ESD and Gnome packages. Now everything is fine again.

[Bryan Quigley (bryanquigley)]

Is this fixed? Or do you still have this issue?

[Bryan Quigley (bryanquigley)]

This is a user configuration error, correct?