On Tue, Aug 28, 2007 at 04:07:20PM -0500, Brian Cameron wrote:
Bryce:
Looking at the logs, it seems that every time GDM tries to start an
XServer that it is hitting the following error:
Aug 28 12:04:12 dorset gdm[5348]: WARNING: gdm_slave_xioerror_handler:
Fatal X error - Restarting :0
No, those are actually intentional failures I'm injecting to trigger the
failsafe mode. Those are just caused by my invalidating the xorg.conf.
It looks like the real issue occurs later on:
Aug 28 12:04:17 dorset gdm[5375]: DEBUG: gdm_server_spawn: '/etc/gdm/failsafeXServer :0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
Aug 28 12:04:17 dorset gdm[5369]: DEBUG: gdm_server_spawn: Forked server on pid 5375
Aug 28 12:04:17 dorset gdm[5369]: DEBUG: do_server_wait: Before mainloop waiting for server
Aug 28 12:04:17 dorset gdm[5369]: DEBUG: Attempting to parse key string: daemon/GdmXserverTimeout=10
Aug 28 12:04:28 dorset last message repeated 4 times
Aug 28 12:04:28 dorset gdm[5369]: DEBUG: do_server_wait: Server timeout
Aug 28 12:04:28 dorset gdm[5369]: DEBUG: gdm_server_start: After mainloop waiting for server
Aug 28 12:04:28 dorset gdm[5369]: DEBUG: gdm_server_start: Temporary server failure (:0)
It looks to me like gdm has successfully launched the failsafeXServer
but doesn't realize it. It's waiting for some sort of signal from the
failsafe server in do_server_wait(), that I guess isn't getting sent?
Is there some sort of signal I need to have the failsafeXServer send
back to gdm? If so, how is this done?
Also note I'm not doing any of the X authentication - is something
dependent on having the auth keys set up?
Thanks,
Bryce