Bug#548446: [gnome-session] gnome doesn't start since gnome-session upgrade

Sat Sep 26 21:45:16 UTC 2009

On Sat, 2009-09-26 at 15:42 +0200, Josselin Mouette wrote:

> Le samedi 26 septembre 2009 à 09:00 -0400, Wendy Elmer a écrit : 
> > I removed gnome-power-manager and the message 
> > went away but gnome still hangs on starting.  No 
> > backgrounds, splashscreens, panels, etc come up.
> > All that happens is that the screen changes to a solid 
> > color and I see the mouse.  There are no error messages.
> > The screen just hangs.  I can do ctl-alt-F1 and go 
> > to a terminal session and restart gdm and log into the 
> > other userid.  Are there any gnome logs I can look at 
> > for the failing userid?
> 
> Look at ~/.xsession-errors after the lockup.
> 
> Cheers, 

Here is the error file.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20090926/413188a1/attachment-0001.htm>
-------------- next part --------------
/etc/gdm/Xsession: Beginning session setup...

GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))

x-session-manager[9253]: WARNING: Error retrieving configuration key '/desktop/gnome/session/idle_delay': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))

GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))

x-session-manager[9253]: WARNING: Could not parse desktop file /home/brent/.config/autostart/sudo.desktop: Key file does not have key 'Type'

x-session-manager[9253]: WARNING: could not read /home/brent/.config/autostart/sudo.desktop

x-session-manager[9253]: WARNING: Could not parse desktop file /home/brent/.config/autostart/cgmailservice.desktop: Key file does not have key 'Type'

x-session-manager[9253]: WARNING: could not read /home/brent/.config/autostart/cgmailservice.desktop

GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))

x-session-manager[9253]: WARNING: No required applications specified

GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))

GNOME_KEYRING_SOCKET=/tmp/keyring-vKbcqK/socket

SSH_AUTH_SOCK=/tmp/keyring-vKbcqK/socket.ssh

GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))

Failed to get value for `/desktop/gnome/applications/at/visual/exec': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))

** (gnome-volume-control-applet:9672): DEBUG: Disabling debugging

socket(): Address family not supported by protocol

socket(): Address family not supported by protocol

GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))

Failure: Module initalization failed