Forum Replies Created
-
Posts
-
All the symptoms make me think that the Qt app didn’t release a mouse grab.
Which is the Qt version in use?
Check the session files in /usr/NX/var/log/node/C-*:
grep -i encod /usr/NX/var/log/node/C-*/sessionIf you get:
Info: Using H.264 software encoder.
the encoding is done by the CPU, otherwise you’ll get “hardware encoder” if it is done by the GPU.
For Belgian layout I found these:
| (pipe, also known as bar) = right Alt + 1
@ (at) = right Alt + 2 (on some variants, right Alt + A, right Alt + Q)
I’d suggest to check if lightdm/gdm is running. Likely no screen is attached to the video output and display service failed because the video card went into low power mode.
The main difference between terminal services on Windows Server and NoMachine is that latter provides access to the screen of the console seat. In that way you can benefit the graphics acceleration of the video card but limited to one user session.
In your case, the video card looks working in a low-profile mode, very likely because no screen is attached to it. If the card cannot be configured to turn an output on with no screen attached, consider using a fake screen dongle you can attach to the video card (try to search for “headless hdmi dongle”).
debaba, the client doesn’t force a keyboard layout in the server and it is expected. Did you find that behavior changed at some point? Do you know in which version of NoMachine it happened, more or less?
I guess the server changes its resolution automatically in order to match the client. Try to turn off “Match the client resolution upon connecting” in the session display settings.
would you gather log files (see https://www.nomachine.com/AR07K00677) and send them to forum (at) nomachine (dot) com?
Turn “Resize remote screen” on in the display settings. If it doesn’t work, lkely the reason is that remote PC video card hasn’t a screen mode matching the size 5120×2880. You can stretch the screen content over the available client area by turning on the option “Fit to window”, if you find that kind of view is better.
FerdH, thanks for the tip.
By the way, I’ve just updated a Sid system and that symlink looks fixed now.
glxgears runs fine.Hello Constantine. Did you find if the gdm3 issue was related?
I read the log you sent and found your X server was listening on display :1. I’d suggest to pass that display to vglrun:/usr/NX/scripts/vgl/vglrun -d :1 paraviewPlease, give a try to the “xev” test tool. Then gather logs and send to forum (at) nomachine (dot) com : https://www.nomachine.com/DT07M00098