Forum Replies Created
-
Posts
-
ericmock, instead of killing the process, grab a backtrace from it:
gdb -batch -ex "thr apply all bt" -p 12345 > gdb.outwhere 12345 is the pid number. Send us the output.
From https://forums.nomachine.com/topic/manjaro-ubuntu-connection-problem,
can you please execute some commands to collect core stack and send it to us
coredumpctl listYou will receive an output like this:
TIME PID UID GID SIG COREFILE EXE SIZE Thu 2022-07-15 19:48:13 CEST 120316 1000 1000 SIGSEGV present /usr/NX/bin/nxplayer.bin 2.1Mthen depending on the pid number of the nxplayer crash, please execute:
coredumpctl gdb 120316 --debugger-arguments="-batch -ex 'thread apply all bt'" > /tmp/crashReport.txtthen please send us /tmp/crashReport.txt crash report file.
It’s an issue we are aware of and will be fixed in the next software release, version 8. A restart of the nxserver can sometimes help which I can understand is not the best of workarounds, and as akorzy mentioned, didn’t work for him in his case.
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