graywolf

[graywolf]

Latest gdm launches an additional dbus-daemon for the greeter session, triggering the problem. I’m searching for the best way to fix it.

[graywolf]

Hello, could you post the output of glxinfo?

[graywolf]

VNC display has such keyboard mapping. So I think you are running Xvnc in place of Xorg. Check with command: ps -C X,Xorg,Xvnc -f.

 

[graywolf]

I see nothing bad in the log. From what you told me, it could be something different in the clients running on the Windows terminal server. So I’d try to remove NoMachine client on Windows server, then move %USERPROFILE%\.nx elsewhere, and finally re-install NoMachine client.

[graywolf]

Would you collect logs:

1. Enable with /etc/NX/nxserver –debug –enable
2. Replicate the issue
3. Collect with /etc/NX/nxserver –debug –collect
4. Send log archive to forum (at) nomachine (dot) com

 

[graywolf]

All the icons? Is it Gnome or KDE?

[graywolf]

It is not possible to run floating window without any X11 graphics, but I think it wouldn’t make much difference: if I got that right, you have good performance with virtual desktop mode no matter the value of X11VectorGraphics. With X11VectorGraphics “1”, the use of vector and video graphics is the same in both virtual desktop and floating window.

May I ask you to :

1. Set X11VectorGraphics “1”
2. Enable debug mode in server: sudo /etc/NX/nxserver --debug --enable
3. Check “Don’t delete log files on exit” in client Privacy settings
4. Run a test in “virtual desktop” mode
5. Collect statistics: Ctrl+Alt+0, Connection pane, get stats
6. Repeat steps 4 and 5 for “floating window” mode
7. Collect server logs: sudo /etc/NX/nxserver --debug --collect
8. Collect client logs: zip the folder %USERPROFILE%\.nx

Please send results (client log, server log, virtual desktop stats, floating window stats) to: forum (at) nomachine (dot) com

[graywolf]

Using nouveau would make sense if you had an Nvidia card. Intel driver usually has not any problem.

After you changed /etc/gdm3/custom.conf, restarting could help.

Would you tell me the kernel version and the video card information? Commands uname -r and lshw -C display would dump that info.

[graywolf]

Hello, please look at session logs in folders /usr/NX/var/log/node/… That would help to identify the source of the problem.

[graywolf]

Without monitor you get using the NoMachine virtual display (“nxoutput0 connected primary”) that does not use the video card.

In my opinion there is a problem with reading back from the video card related to the nvidia driver. Any chance of trying a different version of the driver?

[graywolf]

H.264 is used in floating window mode to draw those parts of screen that are not built with vector graphics (images, video).

You can search for client log files in your home folder: they have a path like .nx\R-…\session. If you find that session log contains this line, you can say H.264 is in use:

Info: Using H.264 hardware decoder.

Would you send logs for the two cases? Check “Don’t delete log files on exit” in client Privacy settings to be sure they are retained.

 

[graywolf]

No, it is not a lack of features, it is an issue with getting screen changes from the nvidia driver.

In that condition, with monitor disconnected from the system, what you get running from remote: xrandr -q?

 

[graywolf]

You can use nvidia-xconfig to create a new configuration for X.

Have you the chance of trying a different version of Nvidia driver or the open source nouveau driver?

 

[graywolf]

Hello.

Had you turned X11 vector graphics off when trying the custom virtual desktop (in node.cfg: AgentX11VectorGraphics 0)? I’m asking as I’m not sure that is relevant.

Have you notice abnormal increase of network usage in floating window mode?

Could you describe the problem you see? Is it laggy in response to a specific user interaction? Is quality poor because images are blurry, text badly rendered or what? Which applications are you trying in floating window mode?

[graywolf]

Hello. It is intended to match the keyboard of the remote Linux machine having Alt on the left and AltGr on the right. So the left Option is mapped to Alt while the right Option is mapped to AltGr.

You can modify the keyboard map of the remote machine to make Alt and AltGr keys behave in the same way. Be aware that if you follow this way you won’t have Alt key at remote side. To proceed, just run this command in the remote session on Linux:

xmodmap -e "remove mod1 = Alt_L" -e "keycode 64 = ISO_Level3_Shift NoSymbol ISO_Level3_Shift"

 

 

[Author]

Posts