SUMMARY: Help with CDE login problem

From: Thomas Wong (
Date: Tue Apr 07 1998 - 11:17:29 CDT

Thanks to the following folks for their replies:

Sanjaya Srivastava <Sanjaya.Srivastava@Eng.Sun.COM>
David Thorburn-Gundlach <>
"Robert Tayne" <>


My original question is as follows:

Howdy folks. I checked SunSolve and couldn't find the answer to our problem so
I'm turning to Sun Managers for help...

We have just jumpstarted a new Sparc5 (Solaris 2.5.1, Sun recommended patch
cluster, using CDE login) and everything seems find except when I login, it
hangs at the white Solaris logo screen for a good 10 min before it fails and
goes back to the login screen. Upon checking my startlog, I see...

--- Mon Apr 6 13:55:40 PDT 1998
--- /usr/dt/bin/Xsession starting...
--- Xsession started by dtlogin
--- sourcing /van/home2/twong/.dtprofile...
--- sourcing /etc/dt/config/Xsession.d/0050.wdg...
--- sourcing /usr/dt/config/Xsession.d/0010.dtpaths...
--- sourcing /usr/dt/config/Xsession.d/0015.sun.env...
--- sourcing /usr/dt/config/Xsession.d/0020.dtims...
--- sourcing /usr/dt/config/Xsession.d/0030.dttmpdir...
--- sourcing /usr/dt/config/Xsession.d/0040.xmbind...
--- starting /usr/dt/bin/dthello &
--- starting /usr/dt/bin/dtsearchpath
--- starting /usr/dt/bin/dsdm &
--- starting /usr/dt/bin/dtappgather &
--- execing /usr/dt/bin/dtsession...
not sourcing /home/twong/.login (see /home/twong/.dtprofile)
5.0u 0.0s 0:07 67% 0+0k 0+0io 0pf+0w
Segmentation Fault
X connection to :0.0 broken (explicit kill or server shutdown).

The strange thing is, we haven't changed our Jumpstart since last year. And
we've been adding new machines every once in awhile. In fact, we jumpstarted
another Sparc5 a week ago and it works fine. So the question is, what changed?
We rejumped it and same thing. We took a working LX and jumped it and now it
too fails with the same problem. I can still logout/login on existing machines
so must be a jumpstart problem.

This failure doesn't create a core dump. So I have no way of telling what is
actually wrong. Does anyone have any ideas for getting a better error message
then what I have so far? And/or any ideas for what could be wrong?

I edited my .dtprofile to comment out the "dtstart_sessionlogfile" line in hopes
that it will log errors. But the file in my ~/.dt/sessionlogs directory had
zero bytes so still don't know what went wrong.

Thanks in advance.



The answer:

Sanjaya Srivastava <Sanjaya.Srivastava@Eng.Sun.COM> was the closest to the
answer. The suggestion was to set the DISPLAY variable in my .cshrc to
`uname -n`. That didn't work. But that only had the machine name. So I
figured DISPLAY needed a :0 or :0.0. So I tried "machinename:0.0" and it
worked. Hardcoding the machine name is an ugly fix but at least this gets us
going again. Still don't know why the machine we jumpstarted a week ago worked
but this one needed this "fix". But at least we're up and running.

Thanks all.


This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:36 CDT