Britgirl

[Britgirl]

You’re right lo_pan. Although a fix was indeed done and queued up for insertion, it didn’t make the last maintenance. It will definitely be in the next v7 maintenance.

[Britgirl]

Thanks for updating the topic with your solution.

[Britgirl]

Logs received thank you!

[Britgirl]

Just to confirm that we got them, thank you, and we are now able to continue with the investigation.

[Britgirl]

Thanks for letting us know 🙂

[Britgirl]

Codec string: H.264 NVENC/DXVA, audio Vorbis 22kHZ stereo

This shows that NoMachine is actually using hardware decoding. Can you describe the problem you are encountering?

[Britgirl]

NoMachine Terminal Server is targeting organizations with a need for unlimited sessions and/or have a large number of users. Also consider the support that comes with a subscription as well.

For individuals/professionals or very small units, NoMachine Workstation might be a better option 😉

[Britgirl]

Thanks for letting us know anyway, I’m glad a clean reinstall fixed the problem. If it happens again, let us know.

[Britgirl]

If this is a headless Linux machine, please take a look at his article, point 3 in particular:

Connecting to Linux headless machines with NoMachine
https://knowledgebase.nomachine.com/AR03P00973

A specific case which leads to black screen on Linux is when the X server is running but it is not rendering. In this case NoMachine doesn’t use its own virtual display because it detects that the X server running, so you need to turn back on NoMachine’s virtual display. I say “turn back on” because before the system crashed (we can’t be sure if it was the actual connection that crashed), NoMachine was running fine.

[Britgirl]

I’m glad you got the demo up and running. Which product did you choose in the end? 🙂

Out of interest, you wrote “product feature chart shows even the basic versions supporting Web access”. Can you tell me which chart you were looking at? I will make sure it’s corrected.

The comparison of NoMachine Free Edition and Enterprise Desktop is available here: https://www.nomachine.com/remote-access-for-everyone

[Britgirl]

Sorry to hear that. The article I linked included the tips and instructions on how to set key-based authentication with the NoMachine Free Edition, explaining how to add the public key to the server, so I’m not sure why it wouldn’t address your issue. It would have been useful for us to know if one of the steps was not clear or which step didn’t work for you.

We check that NoMachine works out-of-the-box with myriad distributions and an almost endless choice of desktop environments and display managers. So it would have been useful to know which distribution(s) you are using to allow us to investigate internally to make sure that there’s not something we’ve missed.

[Britgirl]

Check the Knowledge Base. It works like that because Linux works like that, a unique operating system in doing so. We include a nxagent virtual X server that you can run, just to make one X server that the system can “see”, one that can run your desktop software and one you can connect to.

The article explaining how to do it is here:

Connecting to Linux headless machines with NoMachine
https://knowledgebase.nomachine.com/AR03P00973

[Britgirl]

Port finished. Will be released as part of the version 8, so shortly. We hope very shortly. It has been a lot of work, as you can imagine, but it will be an important release. Not only because of the M1 port.

[Britgirl]

Can you show me the output of xmodmap -pke? What does xev utility show when the problematic keys are pressed?

[Britgirl]

The logs show that this is not a NoMachine problem. In your case of the big cursor, NoMachine shows it because this is the info that is received from the OS.

[Author]

Posts