fisherman

[fisherman]

I am not sure that I clearly understood what is your problem with crontab and NoMachine. I tried simple command to start application to desired virtual or physical desktop and application did show on required display.

Here is the command I used:
user=fisherman
XAUTHORITY=/home/$user/.Xauthority DISPLAY=:1002 firefox

[fisherman]

Your used resolution are very likely related to the out of memory issue described in following FR – FR09Q03870 – Providing NoMachine Windows packages at 64bit.

[fisherman]

Install output does not say clear information what happened with some files. As I noticed you are installing 32bit package, please can you verify that you are using 32bit OS?

You can check that by executing uname -m

[fisherman]

I need to say yes, you cannot enforce that behavior as NoMachine would still send all displays until that feature is implemented.

Despite this FR05N03113 – Creating a separate video stream for each monitor would be beneficial in your setup, I think what you really need is FR09Q03870 – Providing NoMachine Windows packages at 64bit
since I think that your issue is due to an out of memory problem of 32bit application.

On that regard, please can you tell about resolutions you are using on remote screen.

[fisherman]

Thanks for letting us know. I might not get to New Jersey in the near future, but I can happily accept a virtual beer or coffee 🙂

[fisherman]

I am thinking that you are have selected “Resize remote screen” (see screenshot). For remote resolution to stay the same please use “Enable viewport mode” or “Scale to window”. Please find more information in the article Some tips about resize and scaling options for NoMachine client version 4 or later.

Attachments:

1. 

   Screenshot_resize.png
   

[fisherman]

I think workaround for your case is to call sudo /etc/NX/nxserver --restart just after [removed] start.

[fisherman]

You can create connection files by clicking the Add button in the client top menu, and use them through the Machines User Interface or by directly accessing the NXS files in ~/Documents/NoMachine folder.

More details here:
https://www.nomachine.com/getting-started-with-nomachine

[fisherman]

Possibly DaVinci Resolve is now configured to use PipeWire and you need to select PulseAudio. Can you check possibly if you can select PulseAudio in DaVinci Resolve Preferences > Video and Audio I/O.

[fisherman]

Can you execute after installing pulseaudio following command:
/usr/NX/scripts/setup/nxnode --audiosetup

or check this forum post no-audio-and-microphone-with-pulseaudio

[fisherman]

NoMachine is currently not supporting pipewire, we have opened new Feature Request FR05S04169 – Adding support to PipeWire Sound Server. You can subscribe to the mailing list to be notifed when this FR is implemented by selecting “Notify me when the FR is implemented” and adding your email address.

To be able to use audio in the session we can advice to use workaround mentioned in the Feature Request.

[fisherman]

NoMachine Disk sharing is not supported over the https protocol. You can use Drag&Drop or NoMachine file transfer to transfer files, please see following article: How to transfer files between computers.

[fisherman]

NoMachine does work on Azure Windows OS machine.

Basically procedure to install NoMachine is the same like you did on your local workstation.

[fisherman]

We have open a Trouble Report: TR04S10221 – Authentication fails in NIS environment on Fedora 33 and RHEL 8.

Please follow the link and select “notify me” at the side of the Trouble Report to receive notification of the fix.
Thanks!

[fisherman]

Please can you check this article AR11L00827 – How to connect to NoMachine when the server is behind a NAT router or a firewall.

[Author]

Posts