[FreeNX-kNX] NXAGENT: Fatal IO error on display ...

[Xiong Jiang]

I tried `nxagent :1000.0` directly and it segfaults. So it may just be not 
64-bit ready. Sad to see that 1.4.0 could still work somehow and new version 
has such regression. Did they do test on amd64 at all before releasing it?

On 9/14/05, Fabian Franz <FabianFranz at gmx.de> wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Am Sonntag, 11. September 2005 05:19 schrieb Xiong Jiang:
> > Fatal server error:
> > NXAGENT: Fatal IO error on display
> > "nx/nx,options=/home/jxiong/.nx/C-amd64-1000-
> > 9DE7423FAB451C71475F387B90D6CC0B/options:1000".
> >
> > Info: End of session requested by agent termination.
> > Info: Your session has died before reaching an usable state.
> > Info: This can be due to remote X server refusing access to the client.
> > Info: Please check authorization provided by your X application.
> > Info: Waiting for a further signal to complete.
> > Info: Shutting down the link and exiting.
> >
> > Fatal server error:
> > NXAGENT: Fatal IO error on display
> > "nx/nx,options=/home/jxiong/.nx/C-amd64-1000-
> > 9DE7423FAB451C71475F387B90D6CC0B/options:1000".
> 
> What does the client say? Something like Fake-Cookie mismatch?
> 
> Perhaps you need to change ENABLE_1_5_0_BACKEND to 1
> in /etc/nxserver/node.conf.
> 
> cu
> 
> Fabian
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> 
> iD8DBQFDKLwOI0lSH7CXz7MRAld4AJoCDeQgSLu4T1weo82s3abCaPl6wQCdEneZ
> G3fg7NtlNpKDcdYe2W0iqNQ=
> =78pL
> -----END PGP SIGNATURE-----
> 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20050917/aa9e1ffe/attachment.html>