Forum Replies Created
-
Posts
-
Can you update to the latest version 7.10, both sides, and tell us if you are still experiencing the issue?
Having an “Auto” option is perfectly possible. You will surely ask why we didn’t do that already.
The reason is that, at the time, when we initially evaluated it and decided what to do:
– The situation on the Mac was absolutely all fine and all clear. No problem.
– The situation on Windows was complicated. This setting is exposed only to UWP applications, whereas NoMachine is obviously not, NoMachine is “native”, and it was unclear if there was any “functional bridge”, between this setting and these “go light”, “go dark” events that were exposed to UWP applications and not to “native” ones.
– The situation on Linux… OK, you get it đ
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.