SUMMARY: OpenWindows doesn't start after patching

From: Antonio Figueiredo (antonio@dca.fee.unicamp.br)
Date: Wed Apr 08 1998 - 07:21:04 CDT


Hi

My original question was:

>I installed Solaris 2.5.1 on a Sun machine, and then I logged in and
>ran Open Windows and FVWM, it worked just fine. Afterwards,
>I applied the most recent 2.5.1_Recommended (version date: Mar/19/98)
>patches.
>
>And now, when I try to start OW or FVWM it complains that it
>"can't open display" and the variable DISPLAY is set to ":0".
>So, when I forced to set this variable to "host:0" at my
>.xinitrc it worked.
>

Thanks for all those who replied specially to:
        Casper Dik casper@holland.Sun.COM
        Mark Balwin mark.baldwin@aur.alcatel.com
        Carol Lowry lowry@elrond.sp.TRW.COM
        Dennis Morse dmorse@Morsesoft.COM
        Charly jacobc@comm.mot.com

What caused this misbehavior was the application of the patch 103566-27,
as you see discribed in the thread of the messages below.

Considering the messages, I recommend the following workaround.
Insert in the first few lines of the file /usr/openwin/lib/Xinitrc, the
following DISPLAY settings.

        DISPLAY="`hostname`:0.0"
        export DISPLAY

If the users have the file $HOME/.xinitrc, warn them to insert
define the variable DISPLAY, something like:

HOSTNAME=${HOSTNAME-`hostname`}
export HOSTNAME
DISPLAY=${HOSTNAME}:0.0
export DISPLAY

This problem didn't come out with Solaris 2.6 with all patches
applied SO FAR.

Dennis Morse (dmorse@Morsesoft.COM) wrote a wrapper script for
those applications effected by this patch

Regards,

--antonio

------------------
Antonio Figueiredo www.dca.fee.unicamp.br/~antonio
Computer Engineering & Ind. Automation antonio@dca.fee.unicamp.br
School of Electrical & Computer Engineering afigueiredo@acm.org
State University of Campinas - Campinas, SP BRAZIL +55 19 788-3845

-------------------------------------------------------
>From mark.baldwin@aur.alcatel.com Wed Mar 25 18:05:38 1998

Backout patch 103566-27. Then have a look at the README included with
this patch. It makes some major changes to the way Xsun works.

Regards, Mark...

--
Mark A. Baldwin               -----        mark.baldwin@aur.alcatel.com
UNIX/Security Administrator    ---         (919) 850-6172
Raleigh, NC 27609-7860          -
                     ALCATEL NETWORK SYSTEMS

------------------------------------------------------- >From: lowry@elrond.sp.TRW.COM (Carol Lowry)

The answer to your question is in the README file for patch 103566-27 under "Special Install Instructions."

Carol Lowry (310) 814-6676 TRW lowry@elrond.sp.trw.com One Space Park, R4/2028 Redondo Beach, CA 90278

------------------------------------------------------- >From casper@holland.Sun.COM Wed Mar 25 19:16:37 1998

You probably run fvwm linked against non Solaris libX11.so.

That no longer works with the patch, as teh /tmp/.X11-unix socket has moved. It will be moved back in future.

Casper

------------------------------------------------------- >From dmorse@Morsesoft.COM Wed Mar 25 19:48:04 1998

This is because of the OpenWindows 3.5.1 Xsun patch 103566-27. In the README file the section called Special Instructions has this to say.

All existing applications which are statically linked with the X11 library will have to be relinked with the new library. Or to workaround the problem by setting the DISPLAY environment variable to "hostname:0.0" or "localhost:0.0".

We wrote a wrapper script for those applications effected by this patch.

------------------------------------------------------- >From jacobc@comm.mot.com Wed Mar 25 20:01:50 1998

we had the same problem. it's patch 103566-27 which has some security fixes for Xsun that's causing the problem. either remove this patch or follow the instruction from the readme of the patch:

} Special Install Instructions: } ----------------------------- } } 1. Due to the security issue, previous directories } /tmp/.X11-[pipe|unix] have been relocated to /var/X. } } All existing applications which are statically linked with the } X11 library will have to be relinked with the new library. Or } to workaround the problem by setting the DISPLAY environment } variable to "hostname:0.0" or "localhost:0.0". } } If CDE is running prior to patch installation, user might fail } to login to CDE. To workaround this problem, dtlogin has to } be restarted or reboot the machine.

charly



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