gnome session fails to start after upgrading from 7.10 to 8.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-session (Ubuntu) |
Invalid
|
Medium
|
Ubuntu Desktop Bugs |
Bug Description
I've upgraded from 7.10 to 8.04. Right after reboot I couldn't log in to the gnome session. Failsafe session works, and I can start gnome-session in it. When I do that, there appear many warnings:
leks@warehouse:~$ gnome-session
SESSION_
** (gnome-
** (gnome-
** (gnome-
xrdb: "*Label.background" on line 220 overrides entry on line 150
xrdb: "*Text.background" on line 226 overrides entry on line 191
xrdb: "*Label.foreground" on line 232 overrides entry on line 151
xrdb: "*Text.foreground" on line 238 overrides entry on line 192
** (gnome-
Window manager warning: Failed to read saved session file /home/leks/
Tracker version 0.6.4 Copyright (c) 2005-2007 by Jamie McCracken (<email address hidden>)
This program is free software and comes without any warranty.
It is licensed under version 2 or later of the General Public License which can be viewed at http://
Initialising tracker...
Could not set idle IO priority.
seahorse nautilus module initialized
starting HAL detection for ac adaptors.
none found
Throttle level is 0
evolution-
evolution-
evolution-
** (gnome-
** (gnome-
PID TTY TIME CMD
5632 ? 00:00:00 pulseaudio
This appears to be similar to what I have seen so far on every PC that I have upgraded from gutsy to hardy: after a dist-upgrade, GNOME only appears to work in fail-safe mode. When I select GNOME in non-failsafe mode, the login screen (kdm) disappears but the background stays the blue background of kdm, and nothing happens. Viewing top in one of the terminals reveals a 99% idle CPU; it's as if GNOME has become a large black hole, and remains that way until I press ctrl-alt-backspace.
I run KDE as well on most of my boxes, and that works. Without problems. Starting gnome-settings- daemon from a terminal gives the same hangs, a lot of ALSA messages and a number of xrdb messages:
xrdb: "*Label.background" on line 220 overrides entry on line 150 themes/ Crux/gtk- 2.0/gtkrc: 37: Invalid symbolic color 'fg_color' themes/ Crux/gtk- 2.0/gtkrc: 37: error: invalid identifier `fg_color', expected valid identifier
xrdb: "*Text.background" on line 226 overrides entry on line 191
xrdb: "*Label.foreground" on line 232 overrides entry on line 151
xrdb: "*Text.foreground" on line 238 overrides entry on line 192
/usr/share/
/usr/share/
The strace log explains the hangs, but I don't understand why: htons(16001) , sin_addr= inet_addr( "127.0. 0.1")}, 16) = -1 ETIMEDOUT (Connection timed out)
connect(23, {sa_family=AF_INET, sin_port=
timeout on a localhost connection? What's supposed to be listening on port 16001? There is no firewall active (all policies are ACCEPT). According to some messages on the net, should this be esd?
arno@master:~$ dpkg -S /usr/bin/esd esound- compat: /usr/bin/esd
pulseaudio-
arno@master:~$ sudo netstat -ntlp | grep 16001
[no output]
I'll try to re-login to GNOME and search for port 16001 then.
(btw: the hangs also occur in KDE when I start certain gtk-based apps, most notably firefox and gvim)