Forum Replies Created
-
Posts
-
Try in the server configuration file:
#
# When ‘CreateDisplay’ is enabled, specify the display owner and let
# NoMachine create the new display without querying the user. If the
# server supports only one concurrent connection, the connecting user
# must be the display owner set in this key.
#
#DisplayOwner “”See also this article:
Connecting to Linux headless machines with NoMachine
https://kb.nomachine.com/AR03P00973This sounds like a permissions issue. What workarounds did you already try?
You should take a look at this article in our KB:
How to install NoMachine on macOS Catalina and later
https://kb.nomachine.com/AR11Q01061There is a section for audio issues as well.
Please see the topic https://forums.nomachine.com/topic/manjaro-ubuntu-connection-problem where you will find an explanation and a temporary workaround.
So it could be a different problem, please send the logs to forum[at]nomachine[dot]com. The ones that you originally attached could not be opened (so I’ve removed them from here).
Update: a similar issue has been reported here https://bugzilla.mozilla.org/show_bug.cgi?id=1758473
This is a problem with NVIDIA proprietary drivers and not NoMachine. So please, everyone, you can disable HW decoding as suggested in the reply above as a temporary workaround whilst you wait for a fix for the drivers.
A crash report from another user 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’
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’.
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.
Please follow the topic here: https://forums.nomachine.com/topic/nomachine-client-disconnects-right-after-connection-in-latest-manjaro
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#2Please submit as attachments to forum[at]nomachine[dot]com. Thanks.
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.
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/AR04R01083If 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.
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/DT11R00182Player 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.
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: 4000This 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