Client disconnected immediately after connection established

Forums / NoMachine for Linux / Client disconnected immediately after connection established

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #39250
    gigses
    Participant

    Hi!

    I use Manjaro Linux with latest updates. Also I am using NoMachine Enterprise Client for Linux TAR.GZ x86_64. Yesterday I noticed that client disconnected immediately after connection established. With any hosts. The sound settings window appears, which usually appears after a successful connection. But it closes right away.

    I’ve tried completely uninstalling the NoMachine Enterprise Client and reinstalling it. Did not help.

    How to fix it?

    #39288
    Britgirl
    Keymaster
    #39292
    gigses
    Participant

    Yes, I have tried disabling the setting “Enable hardware accelerated decoding” in $HOME/.nx/config/player.cfg to disable. But it did not help.

    #39297
    Britgirl
    Keymaster

    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).

    #39308
    Britgirl
    Keymaster

    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 list

    You 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.1M

    then depending on the pid number of the nxplayer crash, please execute:
    coredumpctl gdb 120316 --debugger-arguments="-batch -ex 'thread apply all bt'" > /tmp/crashReport.txt

    then please send us /tmp/crashReport.txt crash report file.

    #39309
    gigses
    Participant

    coredumpctl list command output: https://controlc.com/a80d0517

    coredumpctl gdb 120316 --debugger-arguments="-batch -ex 'thread apply all bt'" > /tmp/crashReport.txt
    No match found.

    crashReport.txt is empty

    #39339
    Britgirl
    Keymaster
    coredumpctl gdb 120316 --debugger-arguments="-batch -ex 'thread apply all bt'" > /tmp/crashReport.txt
    No match found.

    You didn’t use the correct player PID. ‘120316’ is the player PID in our example. In your case, in the output of coredumpctl we see PIDS 204956 or 205743 (these are the last 2 we see in the list).

    So run coredumpctl again and this time check the PID number next to the nxplayer process. Use that PID number in “YOURPID”:

    coredumpctl gdb YOURPID --debugger-arguments="-batch -ex 'thread apply all bt'" > /tmp/crashReport.txt

    to get the crashreport.

    #39388
    Britgirl
    Keymaster

    This problem is with the nvidia drivers and not by a NoMachine bug. The same problem was also found in Firefox. They worked around the problem by removing the calls completely. https://bugzilla.mozilla.org/show_bug.cgi?id=1758473

    This does not mean that NoMachine can apply the same workaround. But our own tests show that disabling HW decoding in the player.cfg stops the segfaults. ie.

    Edit the file $HOME/.nx/config/player.cfg and set the configuration key “Enable hardware accelerated decoding” to “disabled”. It’s important to disable this way.

    You could perhaps write on the nvidia forums and check there whether they have a workaround.

     

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.