[comp.windows.x] xlock problem

drich@klaatu.lanl.gov (Dave Rich) (01/18/90)

I'm running X version 11 release 4 on a SparcStation (w/cgthree)
running SunOS 4.0.3c.  When I try to fire up "xlock" I get a
"BadValue" error and it aborts.  I've tried to isolate the problem
somewhat and it seems that xlock cannot create a colormap (in
XCreateDynamicColormap).  I've tried things like using the "-mono"
option with no luck (didn't expect it to work either).  The strange
thing seems to be that down the hall a collegue is running the same
code on a Sun 4/330 with a hi-res monochrome display and xlock works
just dandy for him (he's running SunOS 4.0.3c too).

Any and all help appreciated!

Thanks,

--David Rich (dor@lanl.gov)

janm@eliot.UUCP (Jan Morales) (04/11/90)

A week or two ago I posted to find out why xlock straight from the X11R4
tape would not work.  I have received a fix that solves the problem.  I
also got several requests for the fix.  Since I was not able to e-mail
replies to some of these people (our mailer bites) I'll post here:

  In "xlock.c":

    1. in lines 256 and 268, changed the XGrabPointer arg '-1' to '0'
    2. commented out line 241 (Xfree())

I am not experienced enough in X to know why 2 is needed (or 1 for that
matter) but the fix does seem to work.

Thanks to all who replied.

Jan
-- 
{uunet,pyramid}!pyrdc!eliot!janm