Forum Replies Created
-
Posts
-
Clear. So we will need logs when this behaviour is reproduced. Please submit from both sides, not forgetting the client sides logs as well. Please see the instructions here for those: https://kb.nomachine.com/DT09T00266. For clients side logs please refer to the section “Fourth Step: Collect Client Side Logs”. You can submit them to forum[at]nomachine[dot]com.
If the smartcard has a UBS interface, could you try forwarding the device using the USB option instead? Does it show?
https://kb.nomachine.com/DT09T00266#4.3.Edit: Submit a new topic if the issue re-occurs.
Hi, we are investigating a similar issue, and there is a workaround which you can try. Please check the Trouble Report for details and let us know.
Running the Gnome terminal console in custom session does not work
https://kb.nomachine.com/TR06V11170Hi, maybe your answer is for your other topic? 🙂
Export this smart card reader at session startup does not work
Logs didn’t not reveal any clue as to why it’s happening. Can you update to 8.13 and send us fresh logs?
Edit 10/10/24 – no logs received so investigation was stopped. Please update to the latest version, 8.14, and open a new topic if you continue to have issues., with logs and system journalctl.
We don’t see much difference in the processes besides the Memory Integrity being enabled only on the troublesome system. We can only assume that the differences must lie in the way the two machines are configured. Maybe monitoring to know what happens in system calls could be useful when the player starts?
i) Download Process Monitor https://docs.microsoft.com/en-us/sysinternals/downloads/procmon (it doesn’t require installation)
ii) Right-click on Procmon.exe and select “Run as administrator”
iii) Click on “Filter” in the top menu, then “Filter…”, click “Add” and set the filter:
* Column: Process Name
* Relation: is
* Value: nxplayer.bin
iv) Click “Add” then “Apply”.
v) Click on “File” then “Clear”
vi) Start the NoMachine client, and let Process Monitor capture data for about 30 seconds
vii) Click the magnifying glass icon in the toolbar to stop capturing
viii) Click “File” in the top menu, then “Save…” (PML file)
ix) Create also a TXT summary. Click “File” > “Export…” > “Text File”NoMachine should detect when the X server is not running and run its own virtual display, which is an embedded X server. Please take a look at the article about headless Linux in the knowledge base, paying particular attention to point 1) about stopping the x server manually and restarting the nxserver to allow NoMachine to create its own virtual display.
Connecting to Linux headless machines with NoMachine
https://kb.nomachine.com/AR03P00973You can also disable the GUI permanently, so that it won’t automatically start again after reboot, e.g.:
sudo systemctl disable gdm3Are you using the latest version? It’s now 8.13.
NoMachine is able to connect to Linux physical desktops on Wayland (since version 6). However, there are some limitations with different versions of Wayland desktops and you can read more about connections to Linux desktops running the Wayland display server here: https://kb.nomachine.com/AR02P00969.
You are using KDE Plasma (plasma 6 maybe) on your Fedora 40 server and there is a Trouble Report currently open which looks very much the problem you encountered.
Capture of the Wayland desktop by EGL doesn’t work with KDE Plasma 6
https://kb.nomachine.com/TR05V11141The workaround, besides using x11, can be to use the Gnome Wayland desktop.
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
