segfault on starting a shadow session

I'm experiencing the same problem on Ubuntu 9.04, 32-bit.

In /etc/nxserver/node.conf, I have the following settings:

ENABLE_SESSION_SHADOWING_AUTHORIZATION=0
ENABLE_INTERACTIVE_SESSION_SHADOWING=1
ENABLE_CLIPBOARD="both"
ENABLE_PULLDOWN_MENU=1

I enabled logging, but only see:

-- NX SERVER START: -c /usr/lib/nxserver - ORIG_COMMAND=
-- NX SERVER START: - ORIG_COMMAND=
Info: Using fds #4 and #3 for communications with nxnode.
Info: Using /etc/nxserver/nxacl to change session parameters or deny session.
Info: Closing connection to slave with pid 4176
Info: Closing connection to slave with pid 4176

Note that no file called nxserver is located at /usr/lib/, everything is located at /usr/lib/nx/. Also, I have a dual monitor configuration.

HTH

    -John

I turned logging to debug. See attachment.

I only can reproduce this error when the there is no session running on the
console.

Do you have a running session on the console? Shadowing gdm is not
supported.

Yes, I did have an existing session, with a terminal & gedit running.

 -John

On 6/27/2009 4:05 PM, Marcelo Boveto Shima wrote:
> I only can reproduce this error when the there is no session running on the
> console.
>
> Do you have a running session on the console? Shadowing gdm is not
> supported.
>

I've found the same bug, but it's very strange. In my local area network, shadowing a GNOME session fails ("Connection with remote peer broken" in the client side and "nxagent[4827]: segfault at 2c ip 080e83c7 sp bf89dbe0 error 6 in nxagent[8048000+43e000]" in the server side). But when I move the server to another network shadowing works flawlessly (connecting from local network or through Internet). The server and client configuration it's the same in both cases.

I though it was a problem in my local area network (a strange case of duplicate IPs), but when I fixed the problem, the bug was still there. So looking for help I found this thread.

The server uses the stock configuration provided by the installation package (deb http://ppa.launchpad.net/freenx-team/ubuntu/ jaunty main), and the client is the nomachine windows client (last version, although previous version didn't work too).

I found this bug installing FREENX on ubuntu 9.04 workstations for remote desktop sharing. Shadowing didn't work on the PCs configured and tested on the work office, but worked fine when they was moved to their final location, usually on another office (that is, another network).

I hope this information might help solving this bug...

Hi All,

Using Ubuntu 9.10 - Installed FreeNX as per: https://help.ubuntu.com/community/FreeNX
- The following packages were installed
# freenx-rdp_0.7.3+teambzr104-0ubuntu1~karmic1_all.deb
# freenx-server_0.7.3+teambzr104-0ubuntu1~karmic1_amd64.deb
# freenx-session-launcher_0.7.3+teambzr104-0ubuntu1~karmic1_amd64.deb
# freenx-smb_0.7.3+teambzr104-0ubuntu1~karmic1_amd64.deb
# freenx-vnc_0.7.3+teambzr104-0ubuntu1~karmic1_all.deb
# freenx_0.7.3+teambzr104-0ubuntu1~karmic1_all.deb

From a windows 7 PC running NoMachine NX Client I can create a fresh session using gnome.. i can even shadow that session..
But if i try to shadow the X0 (Local) session the window closes and the following error is shown in the NX Client

Error: Connection with remote peer broken.
Error: Please check the state of your network and retry.

Just to confirm, There is a logged in session on the Ubuntu box.

I have turned on the debugging log level in my node.conf and have attached the nxserver.log for reference.

Let me know if i can provide any other details :)

 - Rob

Can you confirm if this problem happens with the packages from
ppa:freenx-team/testing

Regards

Hi Marcelo,

Thanks for the quick reply however i have a problem.
http://ppa.launchpad.net/freenx-team/testing/ubuntu/dists/karmic/main/binary-amd64/Packages only mentions the neatx packages.

However i can see that the freenx packages are available in the pool
http://ppa.launchpad.net/freenx-team/testing/ubuntu/pool/main/f/freenx-server/

As a result, it would appear i am unable to install freenx using aptitude - Please advise

 - Rob