Britgirl

[Britgirl]

The crash report shows a crash in libnxdixl caused by a call in the nvidia driver. Why this is happening only in Manjaro remains to be seen. For now we suggest you disable hardware decoding on your Manjaro client.

You can disable it completely in the player.cfg. Please edit the file $HOME/.nx/config/player.cfg and set the configuration key “Enable hardware accelerated decoding” to “disabled”. Before changing the configuration key, you should first quit the NoMachine Player (you can do this by right clicking on the !M icon in the system tray and selecting ‘Quit NoMachine Player’.

[Britgirl]

Hi, logs would be useful to be able to help further. Can you send us the logs from the server side? Please follow the instructions here and send them to forum[at]nomachine[dot]com.

https://kb.nomachine.com/DT11R00182

[Britgirl]

Please follow the topic here: https://forums.nomachine.com/topic/nomachine-client-disconnects-right-after-connection-in-latest-manjaro

[Britgirl]

2022-07-15 11:35:25.445 nxplayer[2869:23103] *** WARNING: Textured window is getting an implicitly transparent titlebar. This will break when linking against newer SDKs. Use NSWindow’s -titlebarAppearsTransparent=YES instead.

This is just a warning and is related to the SDK version, which will be updated in version 8.

For the actual error you are receiving “The session negotiation failed: Cannot connect to the requested session”, we will need server-side logs and player logs.

Server -> https://kb.nomachine.com/DT11R00182
Client -> https://kb.nomachine.com/DT11R00181#2

Please submit as attachments to forum[at]nomachine[dot]com. Thanks.

[Britgirl]

Knowing that you were using Fluxbox would have been useful 🙂

We found some issues with the Fluxbox WM which could be related to the problem you encountered. These have been queued up for investigation. I advise you to open a new topic if you have other issues.

[Britgirl]

It’s difficult to say what’s happening. It’s a virtual machine, I assume. We are not aware of any problems connecting to sessions running on Oracle Linux. We even have an Oracle virtual instance with an older version of NoMachine installed and it works fine. Could something have got messed up with the Linux OS configuration?

What’s not clear is whether attempts to connect to the NoMachine 7.6.2 server are still successful from your old laptop. Can you try connecting with another client device? If you get the same error across different clients, the problem is on the server and not the Player side.

If you’re running Wayland on the Linux virtual server,  you should take a look at the tips and suggestions here:

Connecting to a Wayland-based desktop running in a Linux virtual machine
https://kb.nomachine.com/AR04R01083

If that doesn’t help, update the NoMachine software and check if the problem persists. If it does, we’ll be happy to check the server-side logs.

[Britgirl]

Please submit the logs from the server side and submit them to forum[at]nomachine[dot]com.

Collect server side logs automatically
https://kb.nomachine.com/DT11R00182

Player logs may also be useful. Instructions are available here: https://www.nomachine.com/DT11R00181

It’s important you reproduce the problem once you’ve enabled the logs as per the instructions.

[Britgirl]

Hi,

if your computer’s public IP is not displayed in the initial welcome panel, manual configuration of the router may be required (either because the router doesn’t support UPnP or because it is disabled), so that the NoMachine server can be reached over the Internet. We have instructions in our KB on how to enable access to your computer from an external network, https://kb.nomachine.com/AR10R01099#2.

Check out the tutorial we have as well. When you start a connection, by clicking ‘Add’, you insert only the external IP address and port. See the tutorial https://www.nomachine.com/getting-started-with-nomachine#internet, images 11 and 12). There is no need to enter the ‘Configuration’ panel to configure a proxy unless you know what the proxy details are. Have you set up a proxy service? If you haven’t, just ignore that section 🙂

Protocol: NX
Host: 192.168.1.14 (why doesn’t the app say insert internal/external IP here for clarity’s sake?)
Port: 4000

This is for access to your computer when you are on the same network i.e LAN. You should be using the external IP and port (in your case 87.21…xx:20536) The Welcome panels illustrate what to do 😉 but we will bear in mind your suggestion

[Britgirl]

Thanks for letting us know. It’s not the best of boards to choose if you want to use it for desktop work or watch video even. But it depends on how you want to use it 🙂 See a comparison here between the Zero 2 and Pi 4: https://medium.com/@ghalfacree/benchmarking-the-raspberry-pi-zero-2-w-b868accdbb50

[Britgirl]

Can you send us a screenshot of the mac’s “display arrangement” in the Display settings?

[Britgirl]

Hi, it could be a problem with drivers. Have you tried separate NoMachine sessions for AMD and nvidia cards? What happens?

Can you try disabling hardware decoding on the client side? To do that, please edit the $HOME/.nx/config/player.cfg and change the ‘Enable hardware accelerated decoding’ key to:

option key=”Enable hardware accelerated decoding” value=”disabled” 

What’s the result?

[Britgirl]

Hi, your last explanation clarifies things a lot 🙂 It’s not a NoMachine issue, it’s a bug in Gnome and is reported on other forums also with other remote desktop tools. You can unlock it by staring starting an ssh terminal to the host as the same username and run the following:

loginctl unlock-sessions

We also suggest to disable automatic screen lock on that machine.

[Britgirl]

Hi, it’s certainly not something we’ve seen during tests and very unusual. We’re not quite sure how NoMachine client hanging could be related to high throughput on the affected device, so logs from the affected client Linux device would be useful in this case.

You should make sure the check box “Don’t delete logs on exit” is ticked in the Player settings -> Security panel, and then reproduce the problem. Detailed instructions on how to gather the client-side logs are available here: https://kb.nomachine.com/DT11R00181#2. Please send them directly to forum[at]nomachine[dot]com making sure to reference the topic title in the subject of your email. Thanks!

[Britgirl]

Hi, this is supported in traditional NoMachine Player sessions via “Grab the mouse input”, but it’s currently not possible with Web Player sessions. We fully understand the utility of being able to lock the mouse in the browser, so we will investigate adding the option to web-based sessions as well.

[Britgirl]

rfemali3, it’s not clear if your topic is about slow response or no image. Which problem are you actually experiencing. I understand that as a headless Linux, NoMachine works well. We have just verified to make sure.

Kroy has been kind and looked in the Rpi documentation for you for some tips. But I think that your question is more appropriate for the RPi forums perhaps because your configuration is not the standard manufacturer’s one.

[Author]

Posts