Forum Replies Created
-
Posts
-
NXSERVER WARNING! Cannot open file ‘C:\Documents and Settings\All Users\\NoMachine\\var\\db\\update’. Error is 13, EACCES, Permission denied.
Please check the access rights to that folder.
We see also error messages about a module that is supposed to be registered to the system and loaded on reboot after installation.
It is possible that module wasn’t updated correctly.
Please let us know the output of command
nxservice64.exe --status nxlsaandnxservice32.exe --status nxlsa(You have to run cmd as Administrator and change directory to %PROGRAMFILES(x86)%\NoMachine\bin in order to run those nxservice commands).Did you try to remove completely the old installation and reboot before installing the latest NoMachine package?
Hello. Did you find a workaround here?
https://forums.nomachine.com/topic/rendering-of-fonts-in-libreoffice-workaround
Hello, it is possible that problem is due to the driver of the video card.
Anyway, I’d like to try to reproduce the same problem. I’d need to know the desktop environment (Gnome, KDE, MATE, etc) you have been using when the problem showed up. That should help to replicate your setup as near as possible.
VirtualGL is of little use if your system has no video card.
You should not set $HOME/utilities/NX/lib in LD_LIBRARY_PATH, I don’t get the reason for setting DISPLAY=:0.0.
If you want to run a virtual display and you have a free version of NoMachine, turn off the display manager (
systemctl stop display-manager), set CreateDisplay and DisplayOwner in /usr/NX/etc/node.cfg, restart the NoMachine server (nxserver --restart).You can setup VirtualGL by the command
sudo /home/harrisromeo/utilities/NX/bin/nxserver --virtualgl-install.Then run paraview with VirtualGL assistance:
/home/harrisromeo/utilities/NX/scripts/vgl/vglrun paraviewPAraView wouldn’t get any problem if it weren’t searching that path for libraries. That should not happen, so I told you to check LD_* in the environment.
ParaView is searching for libraries at a wrong path (/home/harrisromeo/utilities/NX/lib). Please check how LD_LIBRARY_PATH and LD_PRELOAD are set in your environment.
It looks OK. Would you post the content of files $HOME/.nx/node/C-*/options from the server-side host? I’d like to check whether geometry setting is correct there.
Hello lo_pan. I was not able to replicate that issue. Would you post the output of command
xrandr -qfrom your client system?xprop -root | grep XKB returns nothing: I think that is the source of the problem. I suggest you search for the reason the keyboard is not correctly set up on the Ubuntu machine.
Does the workaround in TR08S10329 fix the issue?