Forum Replies Created
-
Posts
-
1) Open the NoMachine UI on your computer -> Player settings -> Input and check option ‘Always show remote cursor pointer’.
Create a new session and see if both cursors jump.
2) Edit node.cfg on the server host and set:
DisplayServerExtraOptions "-nocursorlock"Create a new session and see if both cursors jump.
What do you observe?
Did you install package from our website or from the aur repository? We tried the packages from the aur repo on the fly and they indeed behave in the same way as what you are experiencing.
Related topic: https://forum.nomachine.com/topic/manual-command-entry-needed
For your issue, we’d like to see the stack from the server and also NoMachine logs as well.
On the server side, please see: https://kb.nomachine.com/DT07S00244#1.1
And then the journalctl from the server side as well.
Hi, NoMachine Free Edition is for access to the physical desktop of the remote machine. If, in the past, you used NX Free Edition, which offered what we now call connections “NoMachine virtual desktops”, you probably need NoMachine Workstation. The virtual Linux desktop functionality is a feature of the NoMachine Terminal Server Family.
You can read more about these products on our website at the following links:
NoMachine Free Edition – https://www.nomachine.com/everybody
NoMachine Workstation – https://www.nomachine.com/product&p=NoMachine%20Workstation
Differences between NoMachine Free Edition for Linux and NoMachine Workstation for Linux
https://kb.nomachine.com/AR10K00702What is the difference between physical desktop connection and virtual desktop connection?
https://kb.nomachine.com/AR10K00700Now that the app for mobile is aligned with its fellow desktop and server products, updates to the app will be much more regular. Like we wrote in the software update announcement at the time, “With this important milestone reached, the app can be kept actively aligned with NoMachine server products as development continues to move forward.”
Thanks for this additional info. We suggest you wait for the next mobile update and we can check that it fixes the TR 🙂
The Trouble Report is confirmed and still open. If nxserver is not running, the system info dialog doesn’t show.
You can safely shut down and/or reboot your machine if this message shows.Have you tried reducing the resolution, via Mint’s own system settings?
In System Settings, Accessibility, Desktop Zoom, click Enable zoom. Then you can increase or decrease screen with (Ctrl and +) or (Ctrl and -). If you want to be able to do this within the session, enable grab mouse and keyboard in the Player settings.
The logs did not show anything untoward.
Consider that NoMachine doesn’t use native retina resolution. Support for retina is in the development roadmap, however. What we would expect is that the remote session does not have the same resolution as the local desktop of the mac i.e what you see in the session would be of a lower resolution.
You said that viewport was less blurry than “resize remote”, but in your last follow-up you seem to be saying the opposite. Can you clarify this point?
Hi,
Server logs are from May 25th 1:58, yet player logs do not correspond to the time that a connection attempt was registered on the server. What the server logs do show however is that there is no disk space left (on the SD card), and it’s probably the reason why the display won’t start. What is the GUI or desktop environment running there? It’s important to know so that we can check in our labs. Please contact the person in charge of the Jetson.
Hi Timo, so here’s where we are.
We don’t have your same card, so debugging ourselves is difficult. We use the Intel mediasdk mfx library for Intel QuickSync acceleration and for your specific problem it fails right on the start when we try to initialize the mfx session. It returns every time the MFX_ERR_UNSUPPORTED error, this is what we can see in the logs.
We’ve put together another debug library for you to test (this is our last one), when you have a chance please try it and send the logs as before. I’ll send the link via email as before, so check your inbox.
After that, what we can suggest, if you are able to, is that you test the mfx library with your own set-up by building it yourself.
Here is the link to the library https://github.com/Intel-Media-SDK/MediaSDK/blob/master/api/include/mfxvideo%2B%2B.h
The instructions for building and running it are here: https://github.com/Intel-Media-SDK/MediaSDK and https://github.com/Intel-Media-SDK/MediaSDK#how-to-build
We’ve checked the instructions, you’ll need to install additional development pacakages for libva and libdrm (libva-devel and libdrm-devel). If there is anything missing, the building process tells you what packages are missing, so you should be able to follow along. Tell us whether building it yourself and then running a sample encoder it works or not.