Forum Replies Created
-
Posts
-
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.
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 to prevent the loading.
You could perhaps write on the nvidia forums and check there whether they have a workaround.
What monitor are you actually attaching? What distro is installed on the Raspberry? And did you try the suggestion provided by Kroy? Ultimately, we can look at the logs of a remote connection, player and server sides to verify what’s happening. Send them to forum[at]nomachine[dot]com.
Instructions are here:
https://kb.nomachine.com/DT11R00182
https://kb.nomachine.com/DT11R00181It said “disabled” a few times. Then went to “enabled”. Next thing you know both LAN and also WAN work.
If it happens again, then logs will be useful. I’m glad it’s now working for you 🙂
Images cannot be pasted in to topics, and can be attached using the attach utility included below the text field. Please submit them separately, thanks!
Hi, improvements to the virtual keyboard usage on mobile devices will be implemented in the next update of the app.
why is nxserver looking for user ‘rich’? Any suggestions for this error?
It’s a warning and not an error. You can remove user rich from the usersDB.
sudo /etc/NX/nxserver --userdel richLogs are required from the server side in order to understand what is causing the session to fail. Please follow the instructions here https://kb.nomachine.com/DT11R00182 and then send them to forum[at]nomachine[dot]com.
‘Grab the keyboard input’ option enables the so-called ‘passive grab’ of the keyboard, but it is also possible to enable the ‘active grab’. In order to try this, please quit the NoMachine player application completely (you can do this from the NoMachine icon in the tray) and start it again from the terminal using the following command:
/usr/NX/bin/nxplayer --activegrabAfter that, whilst the session is running, go back to the menu and select the box for enabling ‘grab the keyboard’. Does this help?
Backtrace is empty because the process isn’t running any more. Please follow the instructions from https://forums.nomachine.com/topic/manjaro-ubuntu-connection-problem#post-39275.
Run
coredumpctl listYou will receive 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.
In our example the PID is 120316. You will have a different PID number for the nxplayer process. Please use the PID number that you see in your output of
coredumpctl list.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
coredumpctlagain 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.txtto get the crashreport.
Apologies, I didn’t realise you were using the Wizard on the mobile app to start the connection. The app is not yet aligned with the desktop version, so I confused you no doubt when talking about ‘Configuration’, where you have ‘Advanced’. Also, I mentioned the wrong tutorial. I should have pointed you to the tutorial here: https://www.nomachine.com/getting-started-with-nomachine-for-android. All our tutorials are available in our support section (nomachine.com/all-documents) of the website by the way.
Version 8 of the mobile app will be released after we’ve released version 8 for desktop, and so the wizard will be removed and other elements will be improved to make connection creation as seamless as possible.
I confirm what Fisherman says about SSH. Connections using SSH are not available in the free version.
Hi, please take a look at the answer from zaq in the topic here: https://forums.nomachine.com/topic/nomachine-broken-on-windows-10#post-33133.
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.