Actually, this problem has been fixed for me for several days now. Tpowa and I communicated offlist about this, he sent me a fix to test out which seemed to do the trick, and he then released a new version of freenx soon after that contained the fix. So as long as you're up to date with the latest packages (which you appear to be) and haven't manually overridden any of the configuration (have you?) you should be up and working no problem. Try making sure that your node.conf matches the one in the package.
Beyond that, not much jumps out at me that could be the problem. However, your logs do look very different than what I was seeing. First off, I'm not running with compression - maybe try turning that off and see what happens. There's a few other things I see that are different too, such as: > Info: Using cache file 'C > \DOCUME~1\WANDRU~1\NX73F8~1/cache-unix-kde/S-995AA3A0C7559E6DD > 816F5D5080B846C'. I don't have that message. Maybe try deleting this cache file and trying again? > Warning: No data received from remote proxy within 32 seconds. > Error: Lost connection to peer proxy on FD#8. > Error: Connection with remote peer broken. > Error: Please check the state of your network and retry. I don't have these messages either. It almost sounds like a network timeout (i.e., a firewall problem or something), but I'd be surprised if that's actually the case here since NX uses SSH. You'd either be able to make a connection or not; it wouldn't get blocked partway through the session. I'm a bit stumped here, frankly, but I suspect that whatever these messages are they're the root of your problem. Try googling or searching the nomachine knowledge base and see if there's anything about this. Feel free to post back your progress. I'll try to assist as best I can. HTH, DR > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of waldek > Sent: Tuesday, February 28, 2006 2:43 PM > To: [email protected] > Subject: Re: [arch] NX (and VNC?) problems > > > Rosenstrauch, David wrote: > > > FYI - that new freenx package is still broken. > > > > And Juergen H.'s email on the topic was spot on. Once I > put in the fix he > > suggested (below) NX worked like a charm. > > > > Juergen's fix: > > > > Configure /opt/NX/etc/node.conf: > > > > COMMAND_XAUTH=/usr/bin/xauth > > AGENT_EXTRA_OPTIONS_X="-co /usr/share/X11/rgb -fp > > > /usr/share/fonts/misc,/usr/share/fonts/75dpi,/usr/share/fonts/ > 100dpi,/usr/sh\are/fonts/TTF,/usr/share/fonts/Type1" > > did not help in my case. BTW there's a typo in the TTF path > in the line > above. > > I had been using it before on daily basis, on Saturday I did the major > upgrade to xorg and found out on Monday that it does not work anymore. > > I'm using the latest Windows client which is 1.5.0-138 (I upgraded it > first), the server components: > > $ pacman -Q freenx nxserver nx-common > freenx 0.4.5-1 > nxserver 1.5.0-4 > nx-common 1.5.0-4 > > I added > "COMMAND_XAUTH=/usr/bin/xauth" > AGENT_EXTRA_OPTIONS_X="-co /usr/share/X11/rgb > -fp /usr/share/fonts/misc/,/usr/share/fonts/TTF/,/usr/sh > are/fonts/Type1/,/usr/share/fonts/75dpi/,/usr/share/fonts/100dpi/" > > to the /opt/NX/etc/node.conf as suggested by Juergen. > > Funny thing is that I found that: > > http://www.nomachine.com/ar/view.php?ar_id=AR01C00124 > > they say they would fix the font problem with the version > 1.4.1 and the one > available today is 1.5.0-138. So either they forgot or it > shouldn't be an > issue anymore. > > Any suggestions are welcome, I've been looking on google and > freenx mailing > list already but I might miss something. > > Cheers > > waldek > > the logs are below in case anybody is interested. > > I enabled logging on the server and client and what I'm getting is > (/var/log/nxserver.log): > > -- NX SERVER START: -c /opt/NX/bin/nxserver > HELLO NXSERVER - Version 1.4.0-45-SVN OS (GPL) > NX> 105 hello NXCLIENT - Version 1.5.0 > NX> 134 Accepted protocol: 1.5.0 > NX> 105 SET SHELL_MODE SHELL > NX> 105 SET AUTH_MODE PASSWORD > NX> 105 login > NX> 101 User: waldek > NX> 102 Password: > Info: Auth method: passdb ssh > NX> 103 Welcome to: wolfblade user: waldek > NX> 105 listsession --user="waldek" --status="suspended,running" > --geometry="1024x768x32+render" --typ > e="unix-kde" > NX> 127 Sessions list of user 'waldek' for reconnect: > > Display Type Session ID > Options Depth > Screen Status Se > ssion Name > ------- ---------------- -------------------------------- > -------- ----- > -------------- ----------- -- > ---------------------------- > > > NX> 148 Server capacity: not reached for user: waldek > NX> 105 startsession --session="tanithmagna" > --type="unix-kde" --cache="8M" > --images="32M" --cookie="* > *****" --link="isdn" --kbtype="pc102/en_US" --nodelay="1" > --encryption="1" > --backingstore="never" --ge > ometry="fullscreen" --media="0" --agent_server="" --agent_user="" > agent_password="******"" --screenin > fo="1024x738x32+render" > > &session=tanithmagna&type=unix-kde&cache=8M&images=32M&cookie= > ******&link=isdn&kbtype=pc102/en_US&node > lay=1&encryption=1&backingstore=never&geometry=fullscreen&medi > a=0&agent_server=&agent_user=&agent_pass > word=******&screeninfo=1024x738x32+render&clientproto=1.5.0&us > er=waldek&userip=192.168.12.51&uniqueid= > BB07C565A58E56ADFB840644DD9A2F96&display=1000 > Password: > NX> 1000 NXNODE - Version 1.4.0-45-SVN OS (GPL) > NX> 700 Session id: wolfblade-1000-BB07C565A58E56ADFB840644DD9A2F96 > NX> 705 Session display: 1000 > NX> 703 Session type: unix-kde > NX> 701 Proxy cookie: 2dde2fd3df600832c6aabc811b8c8aa5 > NX> 702 Proxy IP: 127.0.0.1 > NX> 706 Agent cookie: 2dde2fd3df600832c6aabc811b8c8aa5 > NX> 704 Session cache: unix-kde > NX> 707 SSL tunneling: 1 > NX> 710 Session status: running > NX> 1002 Commit > NX> 1006 Session status: running > NX> 105 bye > Bye > NX> 999 Bye > NX> 1009 Session status: terminating > NX> 1006 Session status: closed > NX> 1001 Bye. > > > and on the client side: > > session log: > > NXPROXY - Version 1.5.0 > > Copyright (C) 2001, 2005 NoMachine. > See http://www.nomachine.com/ for more information. > > Info: Proxy running in client mode with pid '1976'. > Info: Synchronizing local and remote caches. > Info: Handshaking with remote proxy completed. > Info: Using cache parameters 4/262144/8192KB/8192KB. > Info: Using image cache parameters 1/1/32768KB. > Info: Using isdn link parameters 4096/8/20/100. > Info: Using pack method '16m-jpeg-5' with session 'unix-kde'. > Info: Using ZLIB data compression level 6. > Info: Using ZLIB data threshold set to 32. > Info: Using ZLIB stream compression level 9. > Info: Using remote ZLIB data compression level 6. > Info: Using remote ZLIB stream compression level 9. > Info: Using cache file 'C > \DOCUME~1\WANDRU~1\NX73F8~1/cache-unix-kde/S-995AA3A0C7559E6DD > 816F5D5080B846C'. > Info: Starting X protocol compression. > Info: Established X server connection. > Info: Using shared memory support in X server. > Warning: No data received from remote proxy within 32 seconds. > Error: Lost connection to peer proxy on FD#8. > Error: Connection with remote peer broken. > Error: Please check the state of your network and retry. > > > errors log: > > Proxy: PANIC! Lost connection to peer proxy on FD#8. > Loop: PANIC! No shutdown of proxy link performed by remote proxy. > > > > > > _______________________________________________ > arch mailing list > [email protected] > http://www.archlinux.org/mailman/listinfo/arch > ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ============================================================================== _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
