Comment 8 for bug 371533

another bunch of tests.

Right after boot I tried a normal gnome session login.
The session did not start at all (screen went blank and the gdm login screen reappeared).
psax_after-gnome-session-autologout is the "ps -ax" after this.
.xsession-errors_gnome-session-autologout is taken at this point.
I started a gnome session in the same way and this time I got an apparently good screen (panels with applets, icons, ...) but absolutely non-functional (not even refresh after vt switch); only the mouse pointer was working.
I killed the session with "sudo /etc/init.d/gdm stop".
psax_after-gdm_stop is the "ps -ax" at this point.
notice a lot of zombies and some strangely duplicated tasks.
I tried to start a gnome session once more (after a "sudo /etc/init.d/gdm start", obviously) and this time I got the "Your session..." error message.
psax_after-gdm_start_and_login_with_error is the "ps -ax" at this point.
.xsession-errors is taken at this point.
I then rebooted and used the terminal-login+manual-gnome-session to get to a somewhat working status and write this.
This status is *not* fully functional and I see in the terminal whwe I started gnome-session things like:

(firefox:3902): GnomeUI-WARNING **: While connecting to session manager: Could not open network socket.
** (update-notifier:3837): DEBUG: /usr/lib/update-notifier/apt-check returned 0 (security: 0)
** (update-notifier:3837): DEBUG: crashreport_check

** (gnome-terminal:4011): WARNING **: Failed to connect to the session manager: Could not open network socket

Completely reinstalling this Laptop is (unfortunately) not an option.
I will try to install KDE and see if that works better (I do not like KDE, but...).

All this started when I upgraded to Jaunty.
I might have done a ad error doing so.