Britgirl

[Britgirl]

Steve, if you contact us through the website at the following link, https://www.nomachine.com/support/report-an-issue, with all the details, our Support team will be able to help, including opening a ticket on your behalf if necessary. They will also be able to investigate the issue of not being able to login.

[Britgirl]

Hi Bunnicus,

sorry for the delay in coming back to you and thanks for the logs. We were able to reproduce the same problem. In the logs we found:

type=AVC msg=audit(1755101315.423:1525): avc:  denied  { read } for  pid=1 comm="systemd" name="nxserver.service" dev="sda6" ino=5429691 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:nx_unit_file_t:s0 tclass=file permissive=1

It is reproducible when apparmor is disabled and SELinux enabled. A fix is already scheduled, not for the next release due in the next couple of weeks, but the one after that. In the meantime, the workaround is to enable AppArmour and keep SELinux disabled.

[Britgirl]

Thanks for those. We’re sending you a new debug library – this will let us narrow down the investigation. Submit everything just as before.

[Britgirl]

Great 🙂 we’ll make sure this is added to the appropriate article. Thanks for sharing!

[Britgirl]

Hi, absolutely. NoMachine can be installed in silent/very silent mode on Windows. There is an article with instructions on how to do that here: https://kb.nomachine.com/AR07K00682. To do it remotely, as an admin user, you’ll have to first connect to the target host over SSH or similar tool.

You can also leverage the --networkadd key to add the machine to Network and set its availability, i.e. lock it down to your email address (or others).

nxserver --networkadd [--visible-set all|<list>|nobody]
[--accessid [<code>]|--noaccessid]

Publish this computer in the NoMachine Network. By default it is
visible to all users, this corresponds to option '--visible-set all'.
Use '--visible-set <list>' to provide a comma-separated list of Ids
of NoMachine Network users who will be able to see this computer or
use '--visible-set nobody' to hide this computer to all users.
A random access ID code is assigned by default, otherwise
set a nine numbers code by means of '--accessid <code>'. Specify
--noaccessid to not use the access ID code.

[Britgirl]

Hi Fritz, check the macOS’s screen recording permissions. If NoMachine is there, remove and add again.

[Britgirl]

Hi, we are going to send you a debug library (check your inbox after reading this) which will help us further with the investigation. The output you provided was useful but we need more info.

Once you’ve downloaded the library, run these commands:

sudo cp /usr/NX/lib/libnxdimi.so libnxdimi.so.ori
 
sudo cp libnxdimi.so /usr/NX/lib/
 
sudo /etc/NX/nxserver --restart

Reproduce the behaviour and then send us a new backtrace and logs as before.

[Britgirl]

Please take a look at the following similar topics:

Windows credentials with autologin

and

Connecting to NoMachine on Windows requires password

[Britgirl]

Hi,

are you referring to the actual real monitor (server-side) which remains asleep or do you mean that in the session window it stays blank?

A possible workaround is to change the DisplayServerExtraOptions key which changes the screen grabbing method. It’s in the node.cfg file on the Mac server host. Look for the DisplayServerExtraOptions “” , remove the prepending # and change it to this: DisplayServerExtraOptions “-nosckgrab”. Restart the NoMachine server. Then try to reproduce the issue again.

[Britgirl]

Which problem exactly does it fix?

This: “-alteventapi 1” -> No input.

[Britgirl]

Hi, we have a patch which fixes the problem, let us know if you’d like to try it. We can send you a download link to a free edition package. The patch is scheduled for release in the next update.

[Britgirl]

Hi, in some cases software encoding is used if the resolution is higher than full HD. This could be what is happening. But to be sure, are you able to send us the server-side logs so we can check them? Reproduce the problem, then extract them using the instructions here: https://kb.nomachine.com/DT08U00298#1. Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

It’s strange you didn’t get a notification. We’ll investigate this internally. Thanks for letting us know anyway.

[Britgirl]

Hi, I was about to reply to your other post which is in https://forum.nomachine.com/topic/mic-forward-from-win11-to-mint.

We looked at the attachment you submitted, but we need to see NoMachine server logs from the Ubuntu host and Player logs from the Windows 11 machine. You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298

Attach them here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

Logs point to a problem with Gnome, rather than NoMachine. Logs are showing this:

2919520 2919520 2025-08-25 11:02:12 205.757 NXNODE WARNING! Process '/bin/bash --norc -c exec -a - /bin/bash -c '/bin/dbus-launch --exit-with-session gnome-session --session=gnome'' with pid '2919612/2919612' finished with exit code 1 after 1,369 seconds.

NoMachine correctly tries to start a virtual display because it detects that your Linux is headless. But Gnome fails to start. Looking in the journalctl file would identify what is happening with Gnome.

journalctl -b -0 > journal.txt

[Author]

Posts