NX (www.nomachine) Errors after upgrade to 10.2
Hi,
Last Friday, I upgraded to openSUSE 10.2--basically everything is going fine--have been using that distro since 9.3. What's bugging me is that the Nomachine NX client is not working anymore--have not been able to figure out what is wrong. Background: I have upgraded the nxclient, nxnode, and nxserver to the latest patch releases. I get the following error when I test with my remote and localhost: /***** log begins here NXPROXY - Version 2.1.0 Copyright (C) 2001, 2006 NoMachine. See http://www.nomachine.com/ for more information. Info: Proxy running in client mode with pid '21189'. Session: Starting session at 'Fri Dec 15 15:42:26 2006'. Info: Synchronizing local and remote caches. Info: Handshaking with remote proxy completed. Info: Using wan link parameters 768/24/1/0. Info: Using cache parameters 4/4194304/8192KB/8192KB. Info: Using image streaming parameters 50/128/1024KB/3072/384. Info: Using image cache parameters 1/1/32768KB. Info: Using pack method '16m-jpeg-9' with session 'unix-kde'. Info: Using product 'LFE/None/LFEN/None'. Info: Using ZLIB data compression 1/1/0. Info: Not using ZLIB stream compression. Info: No suitable cache file found. Info: Listening for font server connections on port '11018'. Session: Session started at 'Fri Dec 15 15:42:27 2006'. Info: Established X server connection. Warning: Failed shared memory operation with ERR_CODE#10 RES_ID#37 MIN_OP#1 MAJ_OP#129. Info: Using shared memory parameters 0/0. Error: Connection with remote peer broken. Error: Please check the state of your network and retry. Session: Session terminated at 'Fri Dec 15 15:42:27 2006'. **** log ends here / Any ideas? Thanks in advance for your help. |
I'm having a similar error here. I hope it isn't caused by the X.org 7.2 release openSUSE 10.2 ships..
Quote:
Quote:
|
I've managed to fix this problem :):)
first check in $HOME/.nx/F-.... for a 'session' file. It's a log of the session. Mine ended with the error message: Quote:
|
yapp,
Thank you so much for your reply and most of all SOLUTION! :) Would you be able to break that down into a command line-by-line directive for me? Otherwise, I'll take the ball and run with it. Again thanks and Happy Holidays to you!! --Dietrich 'linux_junky' |
Well I would try the following:
- first see if there are any interesting files left in /usr/X11R6/lib/X11/fonts/ e.g. I still had some Windows truetype fonts there. Copy those to your new /usr/share/fonts directories. - then: Code:
fc-cache -fv Happy holidays to you too :) |
This is the tail of what I see in the 'session' log for my last attempt--does this correspond with your issue--seems like the same thing? (thanks yapp!):
############## begin Could not init font path element /usr/X11R6/lib/X11/fonts/misc/, removing from lis t! Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from l ist! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from li st! Could not init font path element /usr/X11R6/lib/X11/fonts/75dpi/, removing from li st! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from l ist! Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from list ! Fatal server error: could not open default font 'fixed' Warning: Parent process appears to be dead. Exiting keeper. ############ end |
That did it yapp (wooo hooo!)
Thanks for the XMAS gift! Best! |
Thanks a bunch!
The solution worked for a clean install of openSuSE 10.2 also! Have a great New Year's celebration!
|
Great.
Yes I did another install of 10.2 and straight up it works with the above steps. Happy New Year Folks! |
Solved on debian: could not open default font 'fixed'
Hi All,
After few dates of googling, I found the solution: Removing package artwiz-cursor NX and all works OK apt-get remove artwiz-cursor Regards Mariano |
All times are GMT -5. The time now is 03:02 PM. |