Forum Replies Created
-
Posts
-
Physical is OK: AgentX11VectorGraphics 0 is implicit in that case. Switching to “virtual” would not provide any leverage. If you want to try it anyway, just turn off Gdm display manager (systemctl stop display-manager): on the next try NoMachine will ask you if you want to create a virtual display server.
In my opinion, VM has not support for video acceleration (OpenGL renderer is llvmpipe, that is CPU renderer) so you get poor gnome performance. Would you consider a more lightweight desktop like Xfce? Otherwise you could try providing more CPU power to the VM in order to get a faster rendering by llvmpipe.
It is good. What about “renderer” in the output from glxinfo (
glxinfo | grep -i renderer)? Please be sure you issue the command remotely through NoMachine.How are DISPLAY vars set? Please run
env | grep DISPWould you verify the kind of NoMachine session? With NoMachine connected to the remote host, press combo Ctrl+Alt+0 and chose Connection information; look at “session type”.
If the type is “virtual desktop” you can try to turn off X11VectorGraphics; in node.cfg, place:
AgentX11VectorGraphics 0. See also this (applies only to virtual desktop session type): https://www.nomachine.com/AR02L00779Windows event viewer could provide useful information, too.
Run “eventvwr.exe” in a command prompt, then select “Windows Logs/Application” from the tree on the left, search for events with Level “Error” about application “Wow.exe”.In the NoMachine server settings, section “Performance”, turn off “Use acceleration for display processing” and restart the server.
Would you tell me the version of Windows you are using?
Hello.
Can you send the file nxdx.log located in the folder %PROGRAMDATA%\NoMachine\var\log\ ?
You can upload it here or send to forum (at) nomachine (dot) com.So the physical screen of the server would show the same problem. Is the server headless, with display manager turned off? In such a case NoMachine would ask you if you want to create a virtual display.
Enable verbose logging:
/etc/NX/nxserver --debug --enable node
/etc/NX/nxserver --debug --enable serverDisable log cleanup in /usr/NX/etc/node.cfg:
SessionLogClean 0Then connect to the remote server and reproduce the problem.
What is the command set in node.cfg (search for DefaultDesktopCommand)? Search log file /usr/NX/var/log/nxserver.log for that command.Would you change scrolling options in System Preferences? Go to Accessibility -> Mouse & Trackpad -> Mouse Options. Try to change scrolling speed and turn “with inertia” into “without inertia”.
As macOS hasn’t NumLock it is always considered in “off” state. When macOS client connects to the server the state of NumLock is synchronized with the client. There isn’t any configuration that can change such behavior.
When I am using logitech M720 mouse, the extra buttons events don’t seem to be passed to Ubuntu.
As the sculpt mouse is working (see my question below) I suspect mac needs some drivers to make logitech work correctly.
How do the extra button work in local application on the mac computer?However, when using my microsoft sculpt mouse backward button is working fine with Ubuntu.
What about the forward button, does it work too?
Please, test the button events with command
xev -event button. What do you get?Press Ctrl+Alt+0 in the NoMachine client, while the remote session is connected. Menu shows up, then click on Connection. Read the session type there.