Hi Brian, The DISPLAY variable is set to "127.0.0.1:0" The ".3" value is a typo.
My previous tests were showing that xwinclip always failed to open the display. This time, I waited until the kdm logon screen was displayed. Provided that the localhost was specified in /etc/X0.hosts, xwinclip would run. Clearly, there is a timing problem here. I added a 30 second delay (some kludges really make me gag :-) and xwinclip runs sucessfully. Does anyone know why xterm waits for the server while xwinclip doesn't? regards Matthew ----- Original Message ----- From: "Brian Genisio" <[EMAIL PROTECTED]> To: "Matthew Donald" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, January 15, 2002 6:25 AM Subject: Re: xwinclip authorisation problem with remote hosts using XDMCP > What is your DISPLAY variable set to? I am a bit confused, since one output > talks about a server going to 127.0.0.1:3.0 . If your X server is on :0, > xwinclip will never be able to connect, regardless of the authorities. > > Will other local X programs run? xterm, xeyes, xwininfo, etc? > > Brian > > > --- Matthew Donald <[EMAIL PROTECTED]> wrote: > > Hi, > > > > There is a problem when using xwinclip with an X server which connects to a > > remote host using XDMCP. > > > > Basically the sequence is this: > > > > 1. Execute "XWin :0 -query some.host.system". Initially, the authorisation > > file contains no records, so the localhost > > has access to the X server by default. I quote from the Xserver man page: > > > > If this file contains any authorization records, the > > local host is not automatically allowed access to the server, and > > only clients > > which send one of the authorization records contained in the file in the > > connection > > setup information will be allowed access. > > > > 2. XDMCP is used to query some.host.system, which then opens a connection > > to the local PC. The first > > thing done is that XDMCP adds an auth record for some.host.system This > > means that localhost loses access > > to the X server. > > > > 3. After XWin starts, xwinclip executes on the local host. It fails with > > the error message: "Could not open display" > > > > Ok, so I added an xhost command, to explicitly allow access: > > > > xhost +127.0.0.1 > > > > I failed with the error messages: > > > > Xlib: connection to "127.0.0.1:0.0" refused by server > > Xlib: Client is not authorized to connect to Server > > > > I read some more about host access, and I created a /etc/X0.hosts file, and > > I deleted the .Xauthority file. > > This caused a different error. XWin failed with the message: "X connection > > to 127.0.0.1:3.0 broken > > (explicit kill or server shutdown)." > > > > I tried running XWin with the '-ac' command line parameter. This is meant > > to open access to all hosts. > > Xwinclip still couldn't open the display. > > > > If XWin is used with a local window manager, this xwinclip (and any other > > client program which runs on the PC) > > will run sucessfully. However, if XDMCP is used to connect to another > > system, then it fails. > > > > I'm completely stuck. Any help would be very appreciated. > > > > regards Matthew > > > > > > > > > __________________________________________________ > Do You Yahoo!? > Send FREE video emails in Yahoo! Mail! > http://promo.yahoo.com/videomail/ >
