X takes to long to show after gdm login

Bug #20638 reported by Nhestor Balingit on 2005-08-31
10
Affects Status Importance Assigned to Milestone
gnome-session (Ubuntu)
Medium
Sebastien Bacher

Bug Description

I installed hoary on a IBM T30 thinkpad, after apt-get update, and apt-get
dist-upgrade, my X takes too long to show up after gdm login. here are the logs
at /var/log/xorg.0.log

Synaptics DeviceOff called
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware.
(II) RADEON(0): [agp] Mode 0x0f000207 [AGP 0x1002/0xcab0; Card 0x1002/0x4336]
Synaptics DeviceOn called
(--) Synaptics synaptics touchpad found
(II) Mouse0: ps2EnableDataReporting: succeeded
Synaptics DeviceOff called
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware.
(II) RADEON(0): [agp] Mode 0x0f000207 [AGP 0x1002/0xcab0; Card 0x1002/0x4336]
Synaptics DeviceOn called
(--) Synaptics synaptics touchpad found
(II) Mouse0: ps2EnableDataReporting: succeeded
Synaptics DeviceOff called
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware.
(II) RADEON(0): [agp] Mode 0x0f000207 [AGP 0x1002/0xcab0; Card 0x1002/0x4336]
Synaptics DeviceOn called
(--) Synaptics synaptics touchpad found
(II) Mouse0: ps2EnableDataReporting: succeeded
Synaptics DeviceOff called
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware.
(II) RADEON(0): [agp] Mode 0x0f000207 [AGP 0x1002/0xcab0; Card 0x1002/0x4336]
Synaptics DeviceOn called
(--) Synaptics synaptics touchpad found
(II) Mouse0: ps2EnableDataReporting: succeeded
Synaptics DeviceOff called
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware.
(II) RADEON(0): [agp] Mode 0x0f000207 [AGP 0x1002/0xcab0; Card 0x1002/0x4336]
Synaptics DeviceOn called
(--) Synaptics synaptics touchpad found
(II) Mouse0: ps2EnableDataReporting: succeeded
Synaptics DeviceOff called
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware.
(II) RADEON(0): [agp] Mode 0x0f000207 [AGP 0x1002/0xcab0; Card 0x1002/0x4336]
Synaptics DeviceOn called
(--) Synaptics synaptics touchpad found
(II) Mouse0: ps2EnableDataReporting: succeeded
Synaptics DeviceOff called
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware.
(II) RADEON(0): [agp] Mode 0x0f000207 [AGP 0x1002/0xcab0; Card 0x1002/0x4336]
Synaptics DeviceOn called
(--) Synaptics synaptics touchpad found
(II) Mouse0: ps2EnableDataReporting: succeeded
Synaptics DeviceOff called
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware.
(II) RADEON(0): [agp] Mode 0x0f000207 [AGP 0x1002/0xcab0; Card 0x1002/0x4336]
Synaptics DeviceOn called
(--) Synaptics synaptics touchpad found
(II) Mouse0: ps2EnableDataReporting: succeeded
Synaptics DeviceOff called

Daniel Stone (daniels) wrote :

Um, by the time gdm starts, X has already loaded. X is the base system for all
graphics, so when your machine flicks out of text mode and you first see a black
screen, the X server is already running.

Nhestor Balingit (nhestor) wrote :

(In reply to comment #1)
> Um, by the time gdm starts, X has already loaded. X is the base system for all
> graphics, so when your machine flicks out of text mode and you first see a black
> screen, the X server is already running.

yes, but it takes me over 5 minutes before the splash screen comes out. i dont
understand.
a freshly installed hoary has no problems, but when i upgrade all packages, this
problem comes out.
i had no problem with this when im using xfree.

Lorenzo E. Danielsson (lordan) wrote :

~/.xsession-errors reports:

/etc/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/gdm/PreSession/Default: running: /usr/bin/X11/sessreg -a -w /var/log/wtmp
-u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "lordan"
/etc/gdm/Xsession: Beginning session setup...
grep: /etc/gconf/1/path: No such file or directory
grep: /etc/gconf/1/path: No such file or directory
/etc/X11/Xsession.d/20desktop-profiles_activateDesktopProfiles: line 138:
/usr/lib/GNUstep/System/Library/Makefiles/user_home: No such file or directory
/etc/X11/Xsession.d/20desktop-profiles_activateDesktopProfiles: line 157:
/usr/lib/GNUstep/System/Library/Makefiles/user_home: No such file or directory
/etc/X11/Xsession.d/30xorg-common_xresources: line 16: XRDBOPTS: command not found
/etc/X11/Xsession.d/30xorg-common_xresources: line 16: XRDBOPTS: command not found
/etc/X11/Xsession.d/30xorg-common_xresources: line 16: XRDBOPTS: command not found
No profile for user 'lordan' found
_IceTransTransNoListen: unable to find transport: tcp
_IceTransmkdir: ERROR: euid != 0,directory /dev/X will not be created.
_IceTransmkdir: ERROR: Cannot create /dev/X
_IceTransPTSOpenServer: mkdir(/dev/X) failed, errno = 13
_IceTransOpen: transport open failed for pts/orthanc.backa97.net:
_IceTransMakeAllCOTSServerListeners: failed to open listener for pts
_IceTransISCOpenServer: Protocol is not supported by a ISC connection
_IceTransOpen: transport open failed for isc/orthanc.backa97.net:
_IceTransMakeAllCOTSServerListeners: failed to open listener for isc
_IceTransSCOOpenServer: Protocol is not supported by a SCO connection
_IceTransOpen: transport open failed for sco/orthanc.backa97.net:
_IceTransMakeAllCOTSServerListeners: failed to open listener for sco
SESSION_MANAGER=unix/orthanc.backa97.net:/tmp/.ICE-unix/6451

** (gnome-session:6451): WARNING **: Host name lookup failure on localhost.
Window manager warning: Failed to read saved session file
/home/lordan/.metacity/sessions/1126733476-10346-392956260.ms: Failed to open
file '/home/lordan/.metacity/sessions/1126733476-10346-392956260.ms': No such
file or directory
Gnome-Message: gnome_execute_async_with_env_fds: returning -1
Gnome-Message: gnome_execute_async_with_env_fds: returning -1
...
...

It also contains loads of (over 4000 when I grep -c -H'ed):

art_render_invoke: no image source given

Possibly related, possibly unrelated, but nautilus and gnome-panel end up eating
all my core and need to be kill -HUP'ed.

Jonathan Jogenfors (etnoy) wrote :

I have the same problem, and from I log in on GDM (which goes very quick to
startup) until I get my GNOME desktop there's probably a 30min delay. In the
meantime I get a lot of the following in my X log:

Synaptics DeviceOff called
Synaptics DeviceOn called
(--) Synaptics Touchpad synaptics touchpad found
(II) Open APM successful
(II) NEOMAGIC(0): Stretching disabled
(II) Configured Mouse: ps2EnableDataReporting: succeeded
Synaptics DeviceOff called
Synaptics DeviceOn called
(--) Synaptics Touchpad synaptics touchpad found
(II) Open APM successful
(II) NEOMAGIC(0): Stretching disabled
(II) Configured Mouse: ps2EnableDataReporting: succeeded

No process is taking any resources, running top in the console shows no cpu usage.

I am running ubuntu breezy, system is updated up to the 27 sept 2005.

Jonathan Jogenfors (etnoy) wrote :

Oh, by the way. I have a Dell Latitude D266XT laptop with a neomagic graphics card.

Sebastien Bacher (seb128) wrote :

is your loopback correctly configured? What does "ping 127.0.0.1" do?

Jonathan Jogenfors (etnoy) wrote :

Loopback is a very probable solution. I'm not at home right now, but I know that
lo has had problems when booting, and that this all feels like a network timeout.
I will check this out as soon as I can.

Daniel Holbach (dholbach) wrote :

Could you follow up on this, so we can probably close the bug.

Nhestor Balingit (nhestor) wrote :

(In reply to comment #8)
> Could you follow up on this, so we can probably close the bug.

yeah. my bad. definitely an interfaces misconfig. all is working now.

Daniel Holbach (dholbach) wrote :

Marking NOTABUG.

Jonathan Jogenfors (etnoy) wrote :

Yes, sorry for my delay. It was an interfaces problem. But shouldn't it be
better if GNOME could send a warning if 127.0.0.1 isn't found? Just a message
box before everything starts?

Sebastien Bacher (seb128) wrote :

a dialog explaining what it is doing would be nice, that's a duplicate of
#20321

Sebastien Bacher (seb128) wrote :

This bug has been marked as a duplicate of bug 26419.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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