Forum Replies Created
June 4, 2021 at 16:17 in reply to: Can’t connect from Linux Mint to Manjaro on local network #33892
As from the error message you mentioned in NoMachine “Authentication failed.” it looks that you did user wrong host username and password.
Please see following article Username formats supported to log-in to NoMachine by password authentication.
I feel that issue is more related to gnome-terminal and its implementation. I found some articles that speaks about problem https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/194.
I noticed additionally when I dont have any user logged on physical display this command worked for me, but i tried on Ubuntu 21.04.
DISPLAY=:1002 dbus-launch gnome-terminal
I am happy that my information helped you.
I would recommend that you try NoMachine Cloud server evaluation NoMachine Cloud Server and setup multi node environment by connecting your local network machines to Cloud Server. Here are some information on how to setup Cloud Server based on your needs AR05R01090 – How to choose the most appropriate Cloud Server setup and configure it to allow access to NoMachine Servers.
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:
XAUTHORITY=/home/$user/.Xauthority DISPLAY=:1002 firefox
Your used resolution are very likely related to the out of memory issue described in following FR – FR09Q03870 – Providing NoMachine Windows packages at 64bit.
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
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.
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 🙂
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.
I think workaround for your case is to call
sudo /etc/NX/nxserver --restartjust after [removed] start.
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-nomachineMay 11, 2021 at 17:48 in reply to: Is the new sound system on Fedora 34 compatible with NoMachine? #33386
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.May 10, 2021 at 17:28 in reply to: Is the new sound system on Fedora 34 compatible with NoMachine? #33369
Can you execute after installing pulseaudio following command:
or check this forum post no-audio-and-microphone-with-pulseaudioMay 5, 2021 at 12:39 in reply to: Is the new sound system on Fedora 34 compatible with NoMachine? #33245
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.