Forum Replies Created
-
AuthorPosts
-
September 6, 2024 at 15:37 in reply to: Help needed with custom scripts for XFCE desktop start/stop in NoMachine #49567
Britgirl
KeymasterTry this instead
nx ALL=(ALL) NOPASSWD: /usr/bin/systemctl start lightdm.service, /usr/bin/systemctl stop lightdm.service
We tested on our Debian with XFCE. Nx will have permission to execute sudo without password but only to start/stop lightdm service.
September 6, 2024 at 15:00 in reply to: After upgrade to Ubuntu 24.04.1 LTS players immediately disconnects #49566Britgirl
KeymasterHi, send that file to forum[at]nomachine[dot]com. Maximum file size is 1024 KB.
Britgirl
KeymasterStrange. Our tests on default Fedora don’t reproduce any problems. We set this:
export PATH=”$PATH:/usr/NX/bin”
in .bashrc, and it works.
Britgirl
KeymasterYou mentioned that you had tried disabling HW decoding, but the crash report indicates that HW decoding is still being loaded. You need to “Quit NoMachine player” before changing it, edit the key to<option key=”Enable hardware accelerated decoding” value=”disabled” /> and save. Open NoMachine and start the session.
Please refer to this article for reference:
September 5, 2024 at 16:03 in reply to: After upgrade to Ubuntu 24.04.1 LTS players immediately disconnects #49556Britgirl
KeymasterThanks for those. It would be useful to also see the submit server-side logs to complete the investigation? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. You can upload them here or send them directly to forum[at]nomachine[dot]com.
Britgirl
KeymasterIt seems a system update overwrote some NoMachine system scripts.
You can try running this command on the server from a terminal
sudo /usr/NX/bin/nxserver --eglcapture yes
.Britgirl
KeymasterOK, if the freezing or strange log out happens again, it would be useful to see the logs from the server. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email.
Britgirl
KeymasterSo the logs are not enabled. Just to clarify, the security section of the Player has an option to enable/disable logs using the checkbox. The Server logs are in Server Status, apologies for that.
https://kb.nomachine.com/DT07S00236#2.4
https://kb.nomachine.com/DT07S00236#3.1So all those entries you are noticing are being triggered by some other event. ~240GB of disk space and folders occuping ~30GB should not be happening. As I said, please submit some samples if it starts happening again.
Britgirl
KeymasterHi, the logs were not complete unfortunately. We need the .nx directory from the gdm user’s home dir (look for ‘/var/lib/gdm3/.nx’). Reproducing the problem should not be required.
September 4, 2024 at 15:16 in reply to: After upgrade to Ubuntu 24.04.1 LTS players immediately disconnects #49541Britgirl
KeymasterHi, try disabling hardware decoding in the player. You can do that by setting the appropriate key in the player.cfg file. Instructions are available here:
https://kb.nomachine.com/AR07U01202
You need to set the key to <option key=”Enable hardware accelerated decoding” value=”disabled” /> to completely disable, making sure to quit the player first (from the tray) before then starting a new session.
Does the session still disconnect?
Please send us the client-side logs (the device you are connecting from). You can gather them using the instructions in the following document https://kb.nomachine.com/DT07S00243, specifically paragraph “Fourth Step: Collect Client Side Logs“.
Britgirl
KeymasterThanks for the player logs.
A crash is observed:
18874 18874 2024-09-03 09:26:14 034,814 ClientSignal: WARNING! Child process ‘18979’ died because of signal ’11’, ‘SIGSEGV’.
It would be useful to see a backtrace from the core file/crash report. Please see the instructions here:
https://kb.nomachine.com/AR09L00810Britgirl
KeymasterCheck that you have not configured NoMachine to keep logs in both the Player and Server settings to start off with (Settings > Player > Security and Settings > Server > Security. Generally, you enable logs when you need to reproduce a problem and then analyse the logs, but you should disable them afterwards.
A large number of M-* and R* could be an indication of something crashing and it would be a good idea to send us an example of what you have, so we can check them. You’ve deleted them now, but if they continue to grow, please submit some examples.
Britgirl
KeymasterHi, please follow the steps in the article:
Connecting to virtual desktop sessions in NoMachine
https://kb.nomachine.com/AR07K00681You need to set the ConnectPolicy key in /usr/NX/etc/server.cfg. Point iv or vi depending on your specific needs should be your case 🙂
Britgirl
KeymasterWe received client side logs, but we need to see the server side logs. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Britgirl
KeymasterWe received server side logs and the client side nxtrace log but no NoMachine player logs from the Windows machine. Please submit those as well. See point Fourth Step: Collect Client Side Logs (if requested) of the document in my previous reply. Thanks.
-
AuthorPosts