Path: utzoo!attcan!uunet!wuarchive!sdd.hp.com!ucsd!celit!billd
From: billd@fps.com (Bill Davidson)
Newsgroups: comp.windows.x
Subject: xlock 2.0 and an NCD-19
Summary: It doesn't fix the access table.
Keywords: xlock X-terminals xhosts server access
Message-ID: <12113@celit.fps.com>
Date: 29 Oct 90 18:32:32 GMT
Organization: FPS Computing Inc., San Diego, CA
Lines: 26

I read the blurb that xlock 2.0 was supposed to support X-terminals.  I
wondered how it could do this and it appears to me that it can't.  Either
that or I am missing something.  I got it moments after it showed up on
expo last night.  I invoked it like this:

	% xlock -display hobbes:0 -remote -mode swarm

It locked the terminal just fine.  After I unlocked it I got this message
on the machine I ran xlock on:

X Error of failed request:  BadAccess (attempt to access private resource denied)
  Major opcode of failed request:  111 (X_SetAccessControl)
  Minor opcode of failed request:  0
  Resource id in failed request:  0x40000004
  Serial number of failed request:  1004
  Current serial number in output stream:  1010

Then when I tried to open a new window I got this:

Xlib:  connection to "hobbes:0.0" refused by server
Xlib:  Client is not authorized to connect to Server
Error: Can't Open display

I can't find the solution in the manual page.  Any ideas?

--Bill Davidson