Andrew:

I assume you are using the GDM display manager and not CDE login.  Note
the two display managers put debug log files in different locations, so
some of the information below may not be useful if you are using CDE
login.  If you want to make sure then just run the following command,
and it will tell you which you are using:

   $ svcs cde-login gdm

>> I recently installed the AI image for 106a for sparc on a Sun Blade 2500 
>> I have here. I understand that local desktop X will not work due to the 
>> XVR-600 drivers and Xorg so I was trying to connect into the X desktop via 
>> xdmcp.
>>
>> However, when I try to login, I select the gnome.desktop session and
>> login, the system allows login but then the X session is instantly 
>> disconnected.

Typically when the Xserver "crashes" after user authentication, this is
caused because there is some problem starting the user session.

Can you try logging into a failsafe session?  To do this, just change
the "session" choice from GNOME to Failsafe and then enter your
username and password.  This will log you into a terminal window
program.  Then start gnome session by hand by running the following
command:

   $ dbus-launch --exit-with-session /usr/bin/gnome-session"

When you do this, are there any useful error or warning messages
echoed back to the terminal screen?

Also, after the problem happens, check the user's $HOME/.xsession-errors
file for any interesting error/warning messages.

If that isn't helpful, then you might try turning on debug in the GDM
configuration file (just set Enable=true in the "[debug]" section of
the /usr/share/gdm/defaults.conf file, and then reboot).  Then recreate
the problem, and you'll notice GDM will have created a bunch of GDM
related debug information in your syslog file (/var/adm/messages).
I'd check that for clues as to what might be going wrong.

> Any errors in the /var/log/gdm/* log files or any gnome session
> log files in your home directory?  (I forget where those are
> captured under gdm/gnome.)

These log files contain Xserver log messages.  These logs can be useful
for tracking down problems caused by the Xserver crashing.  It does not
sound like this is your problem, but I'd still check those also.

Brian


Reply via email to