Forum Replies Created
-
Posts
-
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.
Thanks for the additional info. I confused https://kb.nomachine.com/TR05V11141 with https://kb.nomachine.com/TR04V11131 (The latter was fixed in the latest update). Our developers are currently working on the somewhat complicated KDE issue (TR05V11141), but we are unable to promise a fix in the next maintenance release.
NIPIAN, try the following:
1) disable HW decoding on the machine you are connecting from (instructions here: https://kb.nomachine.com/AR07U01202)
Does that make any difference?
2) If it doesn’t help, disable HW encoding on the machine you are connecting to. ( Go to server settings -> server performance -> uncheck “Use hardware encoding”).
Does that make any difference?
Please see my reply on a similar post: