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

[Marco Passerini]

Hi,

Look at this:

### fresh session ##
$ echo $XAUTHORITY
/home/myusername/.xauth6GGIy3

$ ls -a | grep xauth
.xauth6GGIy3

$ cat .xauth6GGIy3
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**

$ xauth  -f ~/.xauth6GGIy3 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 -a | grep Xauth
.Xauthority

$ cat .Xauthority
[empty]

$ xauth  -f ~/.Xauthority list
[no result]


### restored session ###

$ echo $XAUTHORITY
/home/myusername/.xauth6GGIy3

$ ls -a | grep xauth
[no result]

$ ls -a | grep Xauth
.Xauthority

$ cat .Xauthority
[empty]

$ xauth  -f ~/.Xauthority list
[no result]

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

$ ls -a | grep xauth
[no result]


So... apparently .Xauthority do not have any function, the only cookie 
file used is .xauth**code**. Once I suspend the session the cookie is 
removed and it's not generated anymore.

I made a backup of the cookie before suspending the fresh session, and I 
restored it once the session has been restored. Once the cookie is back 
in place, it works! I can open new windows and everything works fine!

I see now where the problem is... but, how could I fix it ? Does FreeNX 
have problems with the fact that the cookie is called .xauth*code* and 
not .Xauthority? Or is the issue somewhere else?






On 05/12/2011 04:03 PM, chris at ccburton.com wrote:
> Marco Passerini<marco.passerini at csc.fi>  wrote on 12/05/2011 12:50:16:
>
>> 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!]
> What is in your
>           $XAUTHORITY
> envvar ??
>
> What does
>          xauth  -f  ~/.Xauthority list
> give here.
>
>> $xauth list
>> xauth: creating new authority file /home/myusername/.xauthm0c9Gu
> Hmmm. It thinks the cookie file is:- /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
> . . . and again . . .
>
>> $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
> Reconnect, and look at what
>           echo $XAUTHORITY
> says the cookie file is called . . . .
>
> .xauthm0c9Gu maybe.
>
> Where is this filename set ??
>
> If this is your cookie file (and it is being removed), it
> won't be replaced by FreeNX.
>
>
>
>