[FreeNX-kNX] unexpected client connection to vnc-local
Durk Strooisma
durk at kern.nl
Wed Nov 28 08:38:05 UTC 2007
Great work! Thanks!
When I get around it, I may backport those packages to Debian 3.1 (sarge)
and 4.0 (etch).
Durk
> Mark, this patch fixes the issue related to the suspend/resume problems
> by removing calls to nxclient to show a dialog. This causes nxdialog
> to fall back to the basic xdialog method. It seems when desktop
> mirroring is on it causes problems with showing the dialog through
> nxclient. The file attached is a Debian patch, but if you remove the
> dpatch header it is simply a diff file. Remember though that SVN has a
> better resolution as Fabian has mentioned earlier. This is just a
> temporary fix until the next release. I hope to backport those fixes
> from SVN or if you can make a new release Fabian? Then I can update my
> patches and release a new version for Debian/Ubuntu.
>
> BTW If anyone wants to contribute to the Ubuntu forum that I have setup
> please go to:
> http://ubuntuforums.org/showthread.php?t=620057&highlight=freenx
>
> As for your other issue with X0 local sessions I do not know much
> except that I never use it. As far as I know, if you resume that under
> a VNC session type it is supposed to give you a local desktop. I just
> choose new session and that works fine for me. I still haven't been
> able to get VNC proxy to function anyhow. I hope the new version fixes
> that. Fabian, does the new version utilize the shadowing libraries?
>
> On Tue, 27 Nov 2007 12:00:29 +0100, freenx-knx-request at kde.org wrote:
>>
>> Message: 1
>> Date: Mon, 26 Nov 2007 23:59:59 +1100
>> From: "Mark Van De Vyver" <mvyver at gmail.com>
>> Subject: Re: [FreeNX-kNX] unexpected client connection to vnc-local
>> To: "User Support for FreeNX Server and kNX Client"
>> <freenx-knx at kde.org>
>> Message-ID:
>> <389c43e40711260459x1a1f7f2fi6eec8366178b0a92 at mail.gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> Hi Jeremy,
>>
>> On Nov 26, 2007 6:13 PM, Jeremy Wilkins <wjeremy at shaw.ca> wrote:
>>> 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: 2
>> Message-ID: <mailman.70.1196161229.10652.freenx-knx at kde.org>
>>
>> remedied by setting in
>> /etc/nxserver/node.conf:
>>
>> ENABLE_DESKTOP_SHARING=0
>>
>> I _think_ the disconnect behavior I see resembles what I might expect
>> if I had a file:
>>
>> /usr/NX/share/noexit
>>
>> as described in section 5.1 "Run a New Login Dialog When the Session
>> Closes" here:
>> http://www.nomachine.com/documents/configuration/client-guide.php
>>
>> Hope that makes it clearer what I'm experiencing.
>> Would appreciate seeing your patch.
>> Does your patch address both these issues?
>>
>> Thanks
>>
>> Mark
>>> > ----------------------------------------------------------------------
>>> >
>>> > 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
>>> ________________________________________________________________
>>> 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
>>> Don't forget to check the NX Knowledge Base:
>>> http://www.nomachine.com/kb/
>>>
>>> ________________________________________________________________
>>> FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>>> https://mail.kde.org/mailman/listinfo/freenx-knx
>>> ________________________________________________________________
>>>
>>
> ********************************
> --
> Jeremy Wilkins
> 306-382-8977
More information about the FreeNX-kNX
mailing list