[FreeNX-kNX] Re: Problem with Nx, Fluxbox and suspended sessions

[Marco Passerini]

Hi,

I removed .Xauthority and now the results are a bit different:

*** First Session ***

$xauth list
myhostname.com/unix:10 MIT-MAGIC-COOKIE-1 **cookie**
localhost.localdomain:1000 MIT-MAGIC-COOKIE-1 **cookie**
myhostname.com/unix:1000 MIT-MAGIC-COOKIE-1 **cookie**

$ls | grep xauth
.xauthm0c9gu

$xterm
[works fine, it opens a new terminal]

Suspending session...


*** Restored session ***

$ls | grep xauth
[no result!]

$xauth list
xauth: creating new authority file /home/myusername/.xauthm0c9Gu

$ls -a| grep xauth
[no result!]

$echo $SHADOW_XAUTHORITY
/home/myusername/.nx/C-myhostname.com-1000-**code***/authority

$cd /home/myusername/.nx/C-myhostname.com-1000-**code***/
$xauth list
xauth: creating new authority file /home/myusername/.xauthm0c9Guls

$ls | grep xauth
[no result!]

$ls  /home/myusername| grep xauth
[no result!]

$xterm
Xlib: connection to ":1000.0" refused by server
Xlib: No protocol specified
xterm Xt error: Can't open display :1000.0



In /etc/nx/node.conf I have:
COMMAND_START_KDE="/usr/bin/ssh-agent /user/bin/dbus-launch 
--exit-with-session /usr/local/bin/fluxbox"

I also tried with the following, and it still does the same:
COMMAND_START_KDE="exec /usr/local/bin/fluxbox"

I also added:
COMMAND_XAUTH=/usr/bin/xauth











On 05/11/2011 06:09 PM, chris at ccburton.com wrote:
> Marco Passerini<marco.passerini at csc.fi>  wrote on 11/05/2011 14:44:40:
>> The timestamp of .Xauthority dates back to yesterday afternoon.
> Hmmm it should be updated by nxnode when you re-connect . . .
>
>> .Xauthority has a cookie in it, and it does not contain 127.0.0.1, but
>> the public ip of the server.
> Mine has
>          servername/unix:1000  MIT-MAGIC-COOKIE-1  unique-cookie-string
>          localhost:1000  MIT-MAGIC-COOKIE-1  unique-cookie-string
>          localhost:1000  MIT-MAGIC-COOKIE-1  unique-cookie-string
>
> Try a first connection, then run
>          xauth list
> then remove ~/.Xauthority
> then disconnect/reconnect to the session
> and see if it re-creates ~/.Xauthority, from SHADOW_XAUTHORITY
> run
>           xauth list
> again
> see if the cookie is the same.
>
> It might depend on what fluxbox is doing.
>
> Try connecting, running a terminal then reconnecting and running
> a new xterm from the command line within the first terminal.


-- 
Marco Passerini
System Specialist
CSC  IT Center for Science
Mobile: +358 50 381 8424
E-Mail: marco.passerini at csc.fi