Very Computer

I've just installed the latest Solaris recommended Patchset on a Solaris 2.6
machine (sparc 2).

Ever since, the X server has stopped running, dtlogin (started from
/etc/init.d/S99dtlogin) exits with:

"The X-server can not be started on display :0"

I'm frankly puzzled. Why would a patchset trash my X server ? If anyone has
experienced something similar I'd be glad to hear about it. If anyone has a
solution to this problem that would be great.

                -- Rory Chisholm

I too have seen this problem on Sparc 5 machines, but only in the following
situation:

   1) At the CDE "dtgreet" login screen, a user selects "Remote login,
      Choose host from list" from the options menu.
   2) At the CDE "dtchooser" remote login screen, a user selects "Return
      to Login screen" from the options menu.  In the process of trying to
      restart the X-server in order to display the "dtgreet" login screen,
      the message "The X-server cannot be started on display :0" appears
      on the console.

I have been able to successfully restart the X-server by logging into the
afflicted machine and executing the unix command

   # kill -HUP `cat /var/dt/Xpid`

as root, but this is a hassle.

I only see this problem on the Sparc 5 machines, not on Sparc 20, Ultra 2,
Ultra 5, or Ultra 10 machines.  I too would very much like a solution...

- Carl

|>
|> Ever since, the X server has stopped running, dtlogin (started from
|> /etc/init.d/S99dtlogin) exits with:
|>
|> "The X-server can not be started on display :0"
|>
|> I'm frankly puzzled. Why would a patchset trash my X server ? If anyone has
|> experienced something similar I'd be glad to hear about it. If anyone has a
|> solution to this problem that would be great.

Not sure why you saw this problem, but try looking in /var/dt/Xerrors for
possible explanations.

Hugh.

--

|  SRAM Design, Sun Microelectronics, Sun Microsystems, Inc.      |
|  Speaking for myself, not for Sun Microsystems.                 |