GDM take a while to launch gnome

Bug #125057 reported by inflamestory
2
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Every first login after boot, I get the brown ubuntu screen during 55s before gnome starts...
I've tried remove gdm with the --purge option and reinstall it but nothing change...
The log form gdm seems to show something strange :

X Window System Version 7.2.0
Release Date: 22 January 2007
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: Linux Ubuntu
Current Operating System: Linux inflames-laptop 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686
Build Date: 04 April 2007
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Jul 10 14:48:56 2007
(==) Using config file: "/etc/X11/xorg.conf"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
Synaptics DeviceInit called
SynapticsCtrl called.
Synaptics DeviceOn called
Could not init font path element /usr/X11R6/lib/X11/fonts/misc, removing from list!
Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/Type1, removing from list!
Synaptics DeviceOff called
Synaptics DeviceOn called
ProcXCloseDevice to close or not ?
SetClientVersion: 0 9
AUDIT: Tue Jul 10 14:57:34 2007: 6362 X: client 27 rejected from IP 127.0.0.1
AUDIT: Tue Jul 10 14:57:39 2007: 6362 X: client 27 rejected from IP 127.0.0.1
AUDIT: Tue Jul 10 14:57:49 2007: 6362 X: client 27 rejected from IP 127.0.0.1
AUDIT: Tue Jul 10 14:57:54 2007: 6362 X: client 27 rejected from IP 127.0.0.1
Synaptics DeviceOff called
FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; fixing.

So I've tried to enable/disable the TCP and the distant connection with gdmsetup but, again, nothing change.
For information, here is my gdm.conf-custom :

# GDM Configuration Customization file.
#
# This file is the appropriate place for specifying your customizations to the
# GDM configuration. If you run gdmsetup, it will automatically edit this
# file for you and will cause the daemon and any running GDM GUI programs to
# automatically update with the new configuration. Not all configuration
# options are supported by gdmsetup, so to modify some values it may be
# necessary to modify this file directly by hand.
#
# Older versions of GDM used the "gdm.conf" file for configuration. If your
# system has an old gdm.conf file on the system, it will be used instead of
# this file - so changes made to this file will not take effect. Consider
# migrating your configuration to this file and removing the gdm.conf file.
#
# To hand-edit this file, simply add or modify the key=value combination in
# the appropriate section in the template below. Refer to the comments in the
# /usr/share/gdm/defaults.conf file for information about each option. Also
# refer to the reference documentation.
#
# If you hand edit a GDM configuration file, you should run the following
# command to get the GDM daemon to notice the change. Any running GDM GUI
# programs will also be notified to update with the new configuration.
#
# gdmflexiserver --command="UPDATE_CONFIG <configuration key>"
#
# e.g, the "Enable" key in the "[debug]" section would be "debug/Enable".
#
# You can also run gdm-restart or gdm-safe-restart to cause GDM to restart and
# re-read the new configuration settings. You can also restart GDM by sending
# a HUP or USR1 signal to the daemon. HUP behaves like gdm-restart and causes
# any user session started by GDM to exit immediately while USR1 behaves like
# gdm-safe-restart and will wait until all users log out before restarting GDM.
#
# For full reference documentation see the gnome help browser under
# GNOME|System category. You can also find the docs in HTML form on
# http://www.gnome.org/projects/gdm/
#
# NOTE: Lines that begin with "#" are considered comments.
#
# Have fun!

[daemon]
AutomaticLogin=inflames
AlwaysLoginCurrentSession=false
DefaultSession=gnome.desktop
AlwaysRestartServer=true
RemoteGreeter=/usr/lib/gdm/gdmgreeter

[security]
NeverPlaceCookiesOnNFS=false
DisallowTCP=false
CheckDirOwner=false

[xdmcp]

[gui]
GtkRC=

[greeter]
GraphicalTheme=Avio-GDM
GraphicalThemes=happygnome/:circles
Use24Clock=oui

[chooser]

[debug]
Enable=true

[servers]
0=Standard

[server-Standard]
name=Standard server
command=/usr/X11R6/bin/X -br -audit 0
flexible=true

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. Does it happen with an another user? Is your lo network interface correctly configure? Does "ping 127.0.0.1" respond?

Changed in gdm:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
inflamestory (dory-thibault) wrote :

Thx for the answer, the lo network interface seems to work perfectly and the ping respond too. This bug happen with other user as well as with my username...

Revision history for this message
Sebastien Bacher (seb128) wrote :

Do you have a firewall on your network?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you may test this behavior with a newer version of Ubuntu like Gutsy Gibbon you may grab a CD Image from here: http://www.ubuntu.com/testing/ ; Thanks and we appreciate your help.

Changed in gdm:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.