*BSD News Article 49187


Return to BSD News archive

Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!news.mathworks.com!newsfeed.internetmci.com!news.sprintlink.net!news.inc.net!news.moneng.mei.com!news.ecn.bgu.edu!vixen.cso.uiuc.edu!uchinews!woodlawn!mezaucha
From: mezaucha@woodlawn.uchicago.edu (Matthew Edward Zaucha)
Subject: Bug in W32 Accelerated Server and xsetroot?
X-Nntp-Posting-Host: midway.uchicago.edu
Message-ID: <DDrw9p.26I@midway.uchicago.edu>
Sender: news@midway.uchicago.edu (News Administrator)
Reply-To: mezaucha@midway.uchicago.edu
Organization: The University of Chicago
Date: Wed, 23 Aug 1995 16:53:49 GMT
Lines: 22

    Hello. I have been experiencing problems with X when I attempt to use
the 'xsetroot -solid <colorname>' command along with the accelerated W32
server.  The first time I start X everything appears to be fine and I can
do whatever I'd like to do.  But, upon exiting X and restarting, the screen
goes blank and the only way to get out that I have been able to discern is to 
ctrl-alt-del the machine.  I have captured the startup and error messages 
and this is the explanation that X is giving:
	
xinit:  Resource temporarily unavailable (errno 35):  unexpected signal 1

    I am running X11R6 v3.1.1 and FreeBSD 2.0.5, and the problem occurs
when using both twm and fvwm, so the choice of window manager does not
seem to be the culprit. If I do not execute the xsetroot command and choose
a default hatched background or a pixmap background, everything runs well.
I am tending to believe that it is a problem with the W32 server, since 
the xsetroot command works beautifully for me when I decide to use the
unaccelerated XF_SVGA server.  Also, which perhaps could be of interest, 
I have ran X11 and the W32 server on the same system with a virtually 
identical configuration under linux with no problems.  
     Any comments or suggestions would be immensely appreciated.