Forum Replies Created
-
Posts
-
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.
Go to the NoMachine Server settings on the Ubuntu host:
!M icon in the system tray -> Server settings -> Status -> Tick the box “Start the server at system startup”.
Does this answer your question?
When you say remote machine, are you referring to the server side?
Can you show us a screenshot of what you are seeing?
What options in Display are enabled/disabled? (Ctrl-Alt-0 -> Display)
We got the image thanks.
Do you have “Scale to window” disabled (submit a screen of the session menu, Ctrl-Alt-0 -> Display)?
Hi, we don’t currently have a license management product. In the future, we will be bringing license management and reporting to the server side, so this will allow customers to keep track of what is in use and what isn’t. We can’t provide an ETA at the moment.
Linking here the original topic https://forum.nomachine.com/topic/client-on-debian-bullseye-aborts-on-connect
For the NoMachine logs, on the device you are connecting from:
– launch the NoMachine UI on the user’s computer from Programs or Menu
– click on Settings -> Player -> Security
– check Don’t delete log files on exit option
– Connect to the server and reproduce the problem.
– Compress the user’s home/.nx directory containing logs.
– Send the compressed logs archive to NoMachine Support Team by e-mail.On the Raspberry Pi server side, please see https://kb.nomachine.com/DT07S00243.
Also submit the journalctl from the server side as well.
– NoMachine product and version on local and remote machine (free version, Workstation, etc).
– Is the flickering happening with other applications?
– What’s the content of the browser when you observe the flickering? (e.g are you watching a video, is it a regular web page, something else?)
Logs were not useful unfortunately. It seems to be more of a problem with the VM and not NoMachine. We have not noticed similar behaviour during tests (and we test with multiple hypervisor solutions).
Thanks for your contribution. It confirms what I previously wrote. This topic is now going to be closed.
The log you sent is not complete. A full set of logs is required. Please follow the instructions here for the server machine: https://kb.nomachine.com/DT07S00243 and send them via email.
So, in that case, SSH jumphost support is not available. What you could try is placing Cloud Server on the jumphost server? Cloud Server can be used as a gateway to broker connections to desktops/machines that are behind the cloud server, on the corporate network. Take a look at https://kb.nomachine.com/DT06S00225. This could be an option for you if you don’t want to allow direct SSH connections.