Forum Replies Created
-
Posts
-
Version 8.13 fixes just the step with changing name (or removing) /usr/NX/lib/libvpl.so – but the other steps like installing rest of the vpl stack should still be neccessary. You seem to have executed a lot of additional steps. We updated our article in the knowledge base, so you should follow the instructions there?
How to use Intel H.264 HW encoder with NoMachine
https://kb.nomachine.com/AR09O00938Regarding your comment about SW encoding, you should compare nxcodec.bin and nxnode.bin, not just nxnode.bin, if you’re interested 🙂
The system doesn’t allow to set resolutions not supported by the graphical system. But you can set “More space” in Displays configuration and use the native retina display resolution. See the attached image 🙂
Attachments:
We need to see logs from the affected Ubuntu host.
Please enable debug, restart nxserver, connect and then collect logs (using the command
sudo /etc/NX/nxserver --debug --collect). Full instructions are available here: https://kb.nomachine.com/DT07S00243.Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Edit 10/10/24: We have received no logs so cannot investigate. We suggest to uninstall completely and re-install NoMachine (the latest version is 8.14) and open a new topic if you have any issues.
Hi, by “recent updates” do you mean the NoMachine update to 8.12 or 8.13? or are you referring to Tumbleweed updates?
We tested connecting from Windows, configured to use the traditional scroll, to connect to a Mac, and in the remote session the window scroll is traditional i.e the client scroll type is also applied in the NoMachine window. We don’t know about the Mos application might be interfering? What about disabling Mos?
Hi, just to confirm that we understand the issue, do you mean that on your NoMachine Ubuntu host, you cannot see the small “Shared/Not shared” window at all or you see it but cannot change it?
Hello,
“..is it possible to achieve concurrent / simultaneous usage without it interfering the session?”
This is possible only with the NoMachine Terminal Server products available for Linux. The NoMachine for Windows products (free version, Enterprise Desktop, Cloud Server) give access to the physical display of the remote computer. This means that if someone is already logged in to the Windows computer, where you have installed a NoMachine Windows server, whilst you are connecting remotely, you will both see the same desktop and share the same mouse and keyboard input.
See this article for more information: https://kb.nomachine.com/AR10Q01052
Hi, can you try 8.13 which we just released? Our codec devs added some improvements for the loading of libvpl to avoid this problem.
We don’t know how much of the Wayland protocol is used by KDE internally or in the communication with the other apps, but we do know that the communication with our agent uses the X11 protocol 😉 The resize issue, to be honest, doesn’t look like a NoMachine bug.
Hi,
Have you tried running the script from node.cfg? Node.cfg is executed as the running user you could try that. Custom scripts set-up in server.cfg are common to all the users who are accessing the server and are executed by the nxserver program.
There is a Trouble Report open which may affect the outcome https://kb.nomachine.com/TR03V11117. If that doesn’t help, then you could try using one of the terminal server products and run virtual desktops for each of your users, disabling the screensaver for the specific user maybe? NoMachine Workstation, available as evaluation software, provides 4 virtual Linux desktops, each one separate, for User A, B, C and D.
We checked the logs and they are clean. NoMachine handles the resize correctly but then the desktop fails to adapt. You mentioned that you have this problem with startplasma-wayland, but not with startplasma-x11. Even when running the Wayland command, the virtual desktop will fall back to using X11 in any case, because that is the only protocol that NoMachine virtual desktops support at the moment. So the recommended command is startplasma-x11.
