Britgirl

[Britgirl]

Hi,

NoMachine is designed to work out-of-the-box on headless machines, nevertheless, in some cases users can experience a black screen when connecting to the remote host. This can be triggered by multiple factors, such as the GPU model, the graphic card driver or the program which uses the GPU for rendering.

I’m afraid we can’t do anything to fix this, but you could try using a different capture method by adding this line in node.cfg on the server side:

DisplayServerExtraOptions “-nodxgigrab”

and restart the server afterwards (go to Settings -> Server -> Server status -> Restart server). If that doesn’t help, the only option is keep the screen connected when using NoMachine.

[Britgirl]

As you know, the X server display is a communication port used by X applications. Since it is a basic information for an X server, we used it also as an ID for our display servers. Also, it is of course unique since two display servers can’t use the same port, and this is the reason why they’re different. The base port for our servers start by default to 1001 and is increased depending on running displays, free ports, etc. You can change that value through configuration files, if you prefer.

Please note that, when running in mirror mode, our display server doesn’t accept connections on its port, so setting the DISPLAY variable to our display server ID value is useless. On the other side, by changing the correct connection port to your X applications, they’ll fail to connect to your physical display server and open their windows.

[Britgirl]

Hi,

if you want a 1:1 experience (connecting to the physical display) you should have the exact monitor arrangement and resolutions on both sides (client and server) and run it in fullscreen mode.

[Britgirl]

Take a look at this web page which gives instructions on how to add a directory to PATH in Linux https://linuxize.com/post/how-to-add-directory-to-path-in-linux. For example,

for only one account:

export PATH="/usr/NX/bin:$PATH" >> ~/.bashrc

for global (need to be done as root):

export PATH="/usr/NX/bin:$PATH" >> /etc/bash.bashrc

You could use aliases (edit the same files based on whether you want to set globally or locally, and add these lines):

alias nxserver=’/etc/NX/nxserver’
alias sudonxserver=’sudo /etc/NX/nxserver’

alias nxplayer=’/usr/NX/bin/nxplayer’

 

 

 

[Britgirl]

Hi, there isn’t a native package for Windows ARM. However, the NoMachine for Windows package available can install and work on Windows ARM architecture, although services that require drivers such as printing and disks (server side) and USB (both sides) will not be available. Let us know how it goes.

[Britgirl]

Hi, definitely not. Can you send us the logs from both sides? Follow the instructions here to enable debug on the server side (the Win computer you are connecting to). There are instructions also for the Win computer you are connecting from.

https://kb.nomachine.com/DT07S00243

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

[Britgirl]

Can you provide more details about what you’d like to achieve?

[Britgirl]

Just a quick update on this. We are currently evaluating whether to make this possible and how it can be achieved, possibly with a key in the connection file.

[Britgirl]

Clear. So we will need logs when this behaviour is reproduced. Please submit from both sides, not forgetting the client sides logs as well. Please see the instructions here for those: https://kb.nomachine.com/DT09T00266. For clients side logs please refer to the section “Fourth Step: Collect Client Side Logs”. You can submit them to forum[at]nomachine[dot]com.

If the smartcard has a UBS interface, could you try forwarding the device using the USB option instead? Does it show?
https://kb.nomachine.com/DT09T00266#4.3.

Edit: Submit a new topic if the issue re-occurs.

[Britgirl]

Hi, we are investigating a similar issue, and there is a workaround which you can try. Please check the Trouble Report for details and let us know.

Running the Gnome terminal console in custom session does not work
https://kb.nomachine.com/TR06V11170

[Britgirl]

Hi, maybe your answer is for your other topic? 🙂

Export this smart card reader at session startup does not work

[Britgirl]

Logs didn’t not reveal any clue as to why it’s happening. Can you update to 8.13 and send us fresh logs?

Edit 10/10/24 – no logs received so investigation was stopped. Please update to the latest version, 8.14, and open a new topic if you continue to have issues., with logs and system journalctl.

[Britgirl]

We don’t see much difference in the processes besides the Memory Integrity being enabled only on the troublesome system. We can only assume that the differences must lie in the way the two machines are configured. Maybe monitoring to know what happens in system calls could be useful when the player starts?

i) Download Process Monitor https://docs.microsoft.com/en-us/sysinternals/downloads/procmon (it doesn’t require installation)
ii) Right-click on Procmon.exe and select “Run as administrator”
iii) Click on “Filter” in the top menu, then “Filter…”, click “Add” and set the filter:
* Column: Process Name
* Relation: is
* Value: nxplayer.bin
iv) Click “Add” then “Apply”.
v) Click on “File” then “Clear”
vi) Start the NoMachine client, and let Process Monitor capture data for about 30 seconds
vii) Click the magnifying glass icon in the toolbar to stop capturing
viii) Click “File” in the top menu, then “Save…” (PML file)
ix) Create also a TXT summary. Click “File” > “Export…” > “Text File”

[Britgirl]

NoMachine should detect when the X server is not running and run its own virtual display, which is an embedded X server. Please take a look at the article about headless Linux in the knowledge base, paying particular attention to point 1) about stopping the x server manually and restarting the nxserver to allow NoMachine to create its own virtual display.

Connecting to Linux headless machines with NoMachine
https://kb.nomachine.com/AR03P00973

You can also disable the GUI permanently, so that it won’t automatically start again after reboot, e.g.:

sudo systemctl disable gdm3

[Britgirl]

Are you using the latest version? It’s now 8.13.

NoMachine is able to connect to Linux physical desktops on Wayland (since version 6). However, there are some limitations with different versions of Wayland desktops and you can read more about connections to Linux desktops running the Wayland display server here: https://kb.nomachine.com/AR02P00969.

You are using KDE Plasma (plasma 6 maybe) on your Fedora 40 server and there is a Trouble Report currently open which looks very much the problem you encountered.

Capture of the Wayland desktop by EGL doesn’t work with KDE Plasma 6
https://kb.nomachine.com/TR05V11141

The workaround, besides using x11, can be to use the Gnome Wayland desktop.

[Author]

Posts