Forum Replies Created
Check your inbox phm!
Hi, indeed a fix was applied in this package, but we needed you to test it in situ so that we could monitor it if it were to happen again. That both of you say the problem has gone is good news. This fix will be officially added to the next release. Thanks everyone for your cooperation!
We already knew that the Pulseaudio was going to be dropped, we just weren’t sure when 🙂 Thanks for submitting the link to the news!May 23, 2022 at 08:39 in reply to: Correct login only after logging out and logging in again #38696
can you send the steps document to forum[at]nomachine[dot]com directly? Thanks!May 23, 2022 at 08:33 in reply to: NoMachine 7.9.2 on 2022-04-04-raspios-bullseye not working? #38692
Thanks for letting us know.
Just as a side not for all Raspberry users, you can consult the article in our knowledge base which outlines which packages you should install depending on the architecture of your RPi.
Installation & configuration notes for NoMachine Linux Raspberry Pi packages
Quoting said article: To check what architecture your Raspberry based on, open a terminal on your device and run the uname -m command. Some examples:
armv6l – means that you should useARMv6 packages
armv7l – means that you should use ARMv7 packages
aarch64 – means that you should use ARMv8 packagesMay 20, 2022 at 16:01 in reply to: Server settings for authentication fails for domain users #38684
I have sent you an email with the link to a new 7.9.2 package. Please follow the instructions. Thanks!May 18, 2022 at 18:05 in reply to: New version of Manjaro GNOME not compatible with NoMachine #38658
Please submit the screenshot again, directly to forum[at]nomachine[dot]com or upload using the attach tool (instead of pasting it in the reply 😉 )
We’ve been able to reproduce the same behaviour with Karabiner and are investigating further.May 18, 2022 at 11:11 in reply to: Fedora35 SELinux preventing access to file nxserver.service #38653
I’ve sent it on to you via email XNR3g. Check your inbox!May 17, 2022 at 10:52 in reply to: Fedora35 SELinux preventing access to file nxserver.service #38645
Please refer to https://forums.nomachine.com/topic/selinux-is-preventing-systemd-from-ioctl-access-on-the-file-nxserver-service. A .pp file was sent to that user. Would you like to receive it?
Hi, the logs are from the player side, we would also need to see the logs from the server side (the computer you are connecting to) in order to understand better.
Is the remote computer headless? If so, please take a look at the article here, in particular point 3.
Connecting to Linux headless machines with NoMachine
If that doesn’t help, please submit the server logs and send them to forum[at]nomachine[dot]com. Instructions for extracting the logs are here: https://knowledgebase.nomachine.com/DT11R00182
Also tell us the desktop environment that is running on the remote Debian computer.
Hi, we are checking this and will update the topic soon.May 16, 2022 at 10:39 in reply to: NXSERVER ERROR: Session failed, application terminated prematurely #38628
This could be related to ptrace capabilities. Did you enable PTRACE capabilities required by NoMachine?
Please take a look at the document dedicated to running NoMachine software in Docker:
Build and Deploy NoMachine Desktops and Applications in Docker for Linux
There is also a troubleshooting section.
Hi, it could be a permissions issue? Has something changed between the session working and then trying to connect again, like a system update or similar?
To check if it’s permissions, open macOS Settings -> Security & Privacy -> Privacy and add ‘nxnode’ to the list of applications allowed in the accessibility list. If nxnode is already listed, remove and re-add it.
If that doesn’t help, please tell us your macOS version and confirm the version of the NoMachine software that you have installed there.May 12, 2022 at 07:58 in reply to: Server settings for authentication fails for domain users #38605
Hi, strange that you didn’t receive the link. That happened the first time as well :-/ (I will get this checked out). We can of course send it again but we will need to rebuild the debug package for the current 7.9.2 🙂