[FreeNX-kNX] unexpected client connection to vnc-local

[Jeremy Wilkins]

I have also posted earlier about the exact same issue.  I can supply a 
temporary patch that disables this issue and uses the ugly xdialog instead.  
However this should only be temporary.  It seems to have become an issue with 
nxclient 3.0.
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 26 Nov 2007 14:49:48 +1100
> From: "Mark Van De Vyver" <mvyver at gmail.com>
> Subject: [FreeNX-kNX] unexpected client connection to vnc-local
> To: "User Support for FreeNX Server and kNX Client"
> 	<FreeNX-kNX at kde.org>
> Message-ID:
> 	<389c43e40711251949j4e7f9c56pe5386e6e0bce49a7 at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Devs,
>
> I've just upgraded my opensuse 10.2 freeNX to the following:
>
> FreeNX-0.7.1-2.1
> nxclient-3.0.0-68
> NX-2.1.0-126.1
>
> The previous version was working OK except for a 'new' rendering issue
> that I have just posted about
>
> I now notice two unexpected behaviors:
>
> 1) When I try to open a new connect to a remote machine, instead of
> the connection I get the "Available sessions" dialog showing:
> X0 (local), vnc-local, 1920x1200, Running, -----
>
> I have to select 'new' to get a connection.
>
> 2) With a new session now established, using fullscreen mode, I
> usually right click the NX client isonc, then selct "close" on the NX
> client icon to bring up the disconnect/terminate dialog box.  Now,
> this action opens the NX new-connection dialog on the remote
> machine.... so it seems I've lost the ability to disconnect.
>
> I've attached some of the the client and server files.
>
> Any suggestions?
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: errors
> Type: application/octet-stream
> Size: 74 bytes
> Desc: not available
> Url :
> http://mail.kde.org/pipermail/freenx-knx/attachments/20071126/23dc12e4/atta
>chment.obj -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: options
> Type: application/octet-stream
> Size: 129 bytes
> Desc: not available
> Url :
> http://mail.kde.org/pipermail/freenx-knx/attachments/20071126/23dc12e4/atta
>chment-0001.obj -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: session
> Type: application/octet-stream
> Size: 924 bytes
> Desc: not available
> Url :
> http://mail.kde.org/pipermail/freenx-knx/attachments/20071126/23dc12e4/atta
>chment-0002.obj -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: errors
> Type: application/octet-stream
> Size: 152 bytes
> Desc: not available
> Url :
> http://mail.kde.org/pipermail/freenx-knx/attachments/20071126/23dc12e4/atta
>chment-0003.obj -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: options
> Type: application/octet-stream
> Size: 237 bytes
> Desc: not available
> Url :
> http://mail.kde.org/pipermail/freenx-knx/attachments/20071126/23dc12e4/atta
>chment-0004.obj -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: session
> Type: application/octet-stream
> Size: 21295 bytes
> Desc: not available
> Url :
> http://mail.kde.org/pipermail/freenx-knx/attachments/20071126/23dc12e4/atta
>chment-0005.obj
>
> ------------------------------
>
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
>   http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
> ________________________________________________________________
>        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>       https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>
> End of FreeNX-kNX Digest, Vol 39, Issue 49
> ******************************************



-- 
Jeremy Wilkins
306-382-8977