[FreeNX-kNX] Segfault when shadowing session

danny.mcpherson danny.mcpherson at gmail.com
Sat Feb 7 19:44:39 UTC 2009


I have the same issue, even after upgrading to the newest Nomachine client
(3.3.0-6).  An interesting note is that I can shadow an existing FreeNX
session, just not the local X0 session.





Stepan Potocky wrote:
> 
>   Hello,
> I would like to ask you about help. I have Ubuntu 8.04 (32 bit) with
> FreeNX server (0.7.3+svn612) with NXSERVER - Version 3.2.0-74-SVN OS
> (GPL, using backend: 3.3.0). On a client side is MS Windows XP and
> Nomachine's client (3.3.0-3). I am using gdm, Gnome without compiz.
> 
> It works fine with Unix desktop and Gnome. Unfortunately when I try to
> Shadow desktop it doesn't work. Window with available sessions is
> opened where I select my current session (on the server) and I hit
> attach. After establishing connection and opening session window it is
> closed and error message is written "The remote connection with the
> remote server was shut down. Please check the state of your network
> connection."
> According to the log it is due to segmentation fault.
> 
> Can you help me and tell me what could be wrong or how to avoid it?
> 
> 
> In node.conf file I only changed:
>   ENABLE_SESSION_SHADOWING_AUTHORIZATION=0
>   SESSION_LOG_CLEAN=0
> and I enabled logging.
> 
> In my kern.log I found this:
> Jan  7 17:32:40 solea kernel: [20169.045834] nxagent[13747]: segfault
> at 0000002c eip 080e10d2 esp bf980540 error 6
> 
> This is part of nxserver.log:
> NX> 148 Server capacity: not reached for user: .*
> NX> 105 attachsession  --link="isdn" --backingstore="1"
> --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1"
> --strict="0" --composite="1" --media="0" --session="test"
> --type="shadow" --client="winnt" --keyboard="pc102/en_US"
> --id="B638F1811D647B41AEDFD0A959276161" --display="0"
> 
> Info: Using /etc/nxserver/nxacl to change session parameters or deny
> session.
> [...]
> NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.3.0)
> NX> 700 Session id: solea-1002-3B0D9CF92F43AB9FA3F75B40E4559FA7
> NX> 705 Session display: 1002
> NX> 703 Session type: shadow
> NX> 701 Proxy cookie: fff5c59b7fdb7bed1bf6cd4c2a8d3996
> NX> 702 Proxy IP: 127.0.1.1
> NX> 706 Agent cookie: fff5c59b7fdb7bed1bf6cd4c2a8d3996
> NX> 704 Session cache: shadow
> NX> 707 SSL tunneling: 1
> NX> 1009 Session status: starting
> NX> 710 Session status: running
> NX> 1002 Commit
> NX> 1006 Session status: running
> NX> 105 bye
> Bye
> NX> 999 Bye
> Info: Closing connection to slave with pid 12858.
> NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot
> set SESSION_LOG_CLEAN=0 in node.conf and investigate
> "/home/pto/.nx/F-C-solea-1002-3B0D9CF92F43AB9FA3F75B40E4559FA7/session".
> You might also want to try: ssh -X myserver; /usr/lib/nx/nxnode
> --agent to test the basic functionality. Session log follows:
> /usr/lib/nx/nxnode: line 569: 13747 Segmentation fault      (core
> dumped) PATH="$PATH_BIN:$PATH" $COMMAND_NXAGENT $R -name "NX -
> $user@$SERVER_NAME:$display - $session (GPL Edition)" -option
> "$USER_FAKE_HOME/.nx/C-$sess_id/options" $B $FP $AGENT_EXTRA_OPTIONS_X
> :$display 2>&3
> NX> 1006 Session status: closed
> [...]
> 
> And this is last few lines from
> /home/pto/.nx/F-C-solea-1002-3B0D9CF92F43AB9FA3F75B40E4559FA7/session
> file:
> [...]
> nxagentKeyboardProc: Using XKB extension.
> nxagentXkbGetRules: XkbBaseDirectory [/usr/share/X11/xkb].
> nxagentKeyboardProc: Using keyboard model [pc102] with layout [en_US].
> nxagentKeyboardProc: XkbInitialMap [NULL]
> nxagentKeyboardProc: Init XKB extension.
> nxagentKeyboardProc: No current keyboard.
> nxagentKeyboardProc: No keyboard, going to set rules and init device.
> nxagentChangeKeyboardControl: Repeat delay was [65535] interval was
> [65535].
> nxagentChangeKeyboardControl: Repeat delay is now [65535] interval is
> now [65535].
> nxagentChangeKeyboardControl: WARNING! Propagating changes to keyboard
> settings.
> nxagentKeyboardProc: Called for [DEVICE_ON].
> Warning: Parent process appears to be dead. Exiting keeper.
> 
>              Thank you very much
>              Best regards
>                    Stepan
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
> 
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject: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
> ________________________________________________________________
> 
> 

-- 
View this message in context: http://www.nabble.com/Segfault-when-shadowing-session-tp21327264p21892115.html
Sent from the freenx-knx mailing list archive at Nabble.com.




More information about the FreeNX-kNX mailing list