[FreeNX-kNX] Re: Problem with Nx, Fluxbox and suspended sessions
Marco Passerini
marco.passerini at csc.fi
Wed May 11 13:44:40 UTC 2011
Hi,
Here are the answers:
1)
$ set| grep -i display
DISPLAY=:1000.0
It shows this result when the session is a new one, but also with a
resumed session (in which case there's the problem that new windows
don't open).
2)
xauth is in the path, yes
3)
The timestamp of .Xauthority dates back to yesterday afternoon.
4)
.Xauthority has a cookie in it, and it does not contain 127.0.0.1, but
the public ip of the server.
On 05/11/2011 01:55 PM, chris at ccburton.com wrote:
> Marco Passerini<marco.passerini at csc.fi> wrote on 10/05/2011 13:59:00:
>
>> Actually I noticed that if I try to open a new terminal from one of the
>> existing terminals it says:
>>
>> ################################
>> $ xterm
>> Xlib: connection to ":1000.0" refused by server
>> Xlib: No protocol specified
>>
>> xterm Xt error: Can't open display: :1000.0
> [SNIP]
> Is
> xauth
> on the $PATH in the existing
> and see if
> ~/.Xauthority
> has a 127.0.0.1 :1000 cookie in it, and check the date stamp.
>
> What does
> set|grep -i display
> in one of the existing terminals produce AAMOI ??
More information about the FreeNX-kNX
mailing list