Britgirl

[Britgirl]

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!

[Britgirl]

Hi Oilinga,

can you send the steps document to forum[at]nomachine[dot]com directly? Thanks!

[Britgirl]

Thanks for letting us know.

Just as a side note 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
https://knowledgebase.nomachine.com/AR07N00896

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 packages

[Britgirl]

I have sent you an email with the link to a new 7.9.2 package. Please follow the instructions. Thanks!

[Britgirl]

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

[Britgirl]

We’ve been able to reproduce the same behaviour with Karabiner and are investigating further.

Edited: July 8th. Please see this topic for our response on Karabiner.

https://forums.nomachine.com/topic/using-karabiner-on-macos#post-39070

[Britgirl]

I’ve sent it on to you via email XNR3g. Check your inbox!

[Britgirl]

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?

[Britgirl]

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
https://knowledgebase.nomachine.com/AR03P00973

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.

[Britgirl]

Hi, we are checking this and will update the topic soon.

[Britgirl]

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
https://knowledgebase.nomachine.com/DT11R00194

There is also a troubleshooting section.

[Britgirl]

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.

 

[Britgirl]

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 🙂

[Britgirl]

Hi,

Works fine in NX Mobile (even using proxy)

I assume you mean the NoMachine app? And you confirm you can connect to the Windows server without problems. Are you able to ping the Linux host?

Client itself does not generate any logs

Did you select “Don’t delete log files on exit” (Settings -> Player -> Security) and then start the session? (more info here: https://knowledgebase.nomachine.com/DT11R00181#2)

[Britgirl]

When connecting to a Linux desktop and after having inserted the login details in the NoMachine’s authentication dialog, NoMachine does one of the following two things.

1) it detects that a physical display is running on the Linux computer and it connects you to its login window. The display manager dialog requires you to insert your username and password and you are then connected.

2) it DOESN’T detect a display running (e.g it might be headless) and NoMachine then asks “Cannot detect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?”. You then click “yes” and you are connected to a virtual desktop which does NOT require further authentication.

In your case you are experiencing both these cases. After a restart NoMachine is not detecting the display and therefore if you have saved your username and password in the NoMachine login dialog, you won’t be prompted to insert them again i.e the display manager does not issue a login dialog. Other times you connect, NoMachine detects that a physical display exists and therefore connects you to it. You are presented with a login dialog by your Linux Mint system.

That’s the explanation and it is happening because your local Linux session is probably still starting when you try to connect with NoMachine 🙂

Perhaps you could give a few more seconds to your system after a reboot before connecting with NoMachine? For example,  when NoMachine tells you “Cannot detect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?”, select ‘No’ and try connecting again.

[Author]

Posts