[comp.windows.x] X Toolkit Error: Can't Open display

barnes@castor (patrick barnes) (08/13/90)

Recently, everytime I come in after a weekend and unlock my screen, my
Xserver forgets where the display is.  Everything was fine friday, I just
locked the screen and went home.  When I come in and unlocked the screen,
everything seems to work ok as far as executing programs in the
existing applications (like maker, xterms and so on..) Anything I try
to do that requires opening a window gets 
	"X Toolkit Error: Can't Open display"
I'm running X11/R3 on a Sun 3/60 using xdm.  I don't log out, just
lock the screen.  Logout and login corrects the problem.  It doesn't
happen durring the week, over night.  $DISPLAY still equals unix:0.0.

Any ideas what may be happening to my server?

Please respond by e-mail to
	Capt Patrick D. Barnes, USAF  	barnes@cs.nps.navy.mil
	NPGSCOL/Code 52Ba		(408) 646-2830
	Monterey, CA  93943		FAX (408) 646-2814

	Capt Patrick D. Barnes, USAF  	barnes@cs.nps.navy.mil
	NPGSCOL/Code 52Ba		(408) 646-2830
	Monterey, CA  93943		FAX (408) 646-2814

mouse@LARRY.MCRCIM.MCGILL.EDU (08/13/90)

> Recently, everytime I come in after a weekend and unlock my screen,
> my Xserver forgets where the display is.  Everything was fine friday,
> I just locked the screen and went home.  When I come in and unlocked
> the screen, everything seems to work ok as far as executing programs
> in the existing applications (like maker, xterms and so on..)
> Anything I try to do that requires opening a window gets
>	"X Toolkit Error: Can't Open display"

> $DISPLAY still equals unix:0.0.

> Any ideas what may be happening to my server?

/tmp/.X11-unix/X0 is getting removed by some sort of /tmp-cleaning
procedure.  Check with your sysadmin or crontab or wherever such things
get put on your system.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu

keith@EXPO.LCS.MIT.EDU (Keith Packard) (08/13/90)

> Recently, everytime I come in after a weekend and unlock my screen, my
> Xserver forgets where the display is.  Everything was fine friday, I just
> locked the screen and went home.  When I come in and unlocked the screen,
> everything seems to work ok as far as executing programs in the
> existing applications (like maker, xterms and so on..) Anything I try
> to do that requires opening a window gets 
> 	"X Toolkit Error: Can't Open display"

This one may seems mysterious, but has a simple solution.  The X server
rendezvous with the client using a unix domain socket named
/tmp/.X11-unix/Xn (where n is the display number).

When your system goes about cleaning up unused files in /tmp it ends up
removing this file, as the file is only used when a new client connects to
the server.  This causes the X client run on monday morning to be unable to
find the X server.

You'll have to fix the cron entry which deletes unused files in /tmp.