Britgirl

[Britgirl]

Hello, we are planning to improve support for HiDPI displays in a future version (not version 9). With this implementation, NoMachine will be able to capture the screen of the server at native pixel resolution on HiDPI displays, but it will also introduce improvements to the appearance of the user interface on such displays.

[Britgirl]

Hi, the logs we received did not have debug enabled. Please enable debug as described in the instructions in my earlier reply, reproduce the problem again, then gather the logs. An updated journalctl and ps -ef should be provided so that they are aligned. Thank you.

[Britgirl]

Hi, I sent you an email with the link to download the debug package 🙂

[Britgirl]

NoMachine does not provide a package specifically for NixOS, you can check the list of officially supported distributions here: https://kb.nomachine.com/AR07H00568.

You can try installing the tar.gz to another directory and not /usr e.g

sudo tar zxf nomachine...tar.gz -C /opt/
sudo NX_INSTALL_PREFIX=/opt /opt/NX/nxserver --install redhat

[Britgirl]

Hi, thanks for submitting this. If you don’t need the server component for your computer (i.e you don’t want to be able to connect to this computer, but you only want to use it as a device to connect from), you could also try installing Enterprise Client which can also be installed using a regular account (without admin privileges).

[Britgirl]

Hi,

did you install just the client i.e Enterprise Client, or is it a client/server product such as the NoMachine free version? If you installed the latter, is the server running correctly and accessible from the system tray?

When it happens, can you check in the Task Manager if the nxplayer.bin process is running but its window does not open, or is there no nxplayer.bin process open at all?

It would be useful to see the NoMachine logs from the affected Windows host. Look for the .nx directory, on Windows the .nx folder is hidden. To find it, write the following in the address bar or the explorer, for example C:\Users\your_account\.nx). Also send the full nxtrace.log of that excerpt. Please send everything to forum[at]nomachine[dot]com.

[Britgirl]

Yes 🙂 We are preparing it and we will be sending you a link to a package for you to download.

[Britgirl]

Can you forward those logs to forum[at]nomachine[dot]com?

[Britgirl]

Hi, we are not able to reproduce the problem connecting to macOS 14 in our lab. Check that USB sharing is still enabled on the server side.  On the Mac server side, check the node.cfg file:

Disabling USB Forwarding
To forbid USB device sharing it is necessary to uncomment and set a proper value for the EnableUSBSharing key in the node configuration file:
client USB devices on the client can be forwarded to server side and made available within the session.
server USB devices on the server can be connected to the end-user’s machine.
both Client and server USB devices can be connected to remote and local sides respectively.
none Neither client or server USB devices can be connected.

More about this is here: https://kb.nomachine.com/DT10R00171#13.4

Are you responsible for the NoMachine server or was the instance created for you by the provider? It sounds more like an issue with Scaleway.

[Britgirl]

Can you share this dockerfile with us so we can check it? Send it directly to forum[at]nomachine[dot]com.

Similar topics have been submitted in the past

NXFrameBuffer failed to start in Docker

Problems with NoMachine in docker

Redis error after time

but in some cases users didn’t come back to us.

Edited: we have the following document for Docker users https://kb.nomachine.com/DT07S00242. Did you check this already?

[Britgirl]

The same errors are present showing it’s not possible to write to the home directory. NoMachine detects that it’s headless (no x server running) and, as expected, tries to create its own virtual display. But since permissions are not set correctly, it fails.

Also, can you show us the output of the ls -la command for each of these?

/rhome/

/home/DV9G49

/rhome/DV9G49/.nx

You mentioned creating a virtual machine with Debian, what are you using to do that?

[Britgirl]

we were seeing the frame buffer error even without the permissions error? What would be causing it then, if the permission error is removed?

Then yes we need to see the logs without the permissions error. Send them over and we’ll check.

[Britgirl]

oneVPL will be in the next update, 8.12, which is going to be in the next couple of weeks.

[Britgirl]

The next time it happens:

Press Windows key + R to open up a Run dialog box. Then, type “eventvwr.msc” and press Enter to open up the Event Viewer utility.

Inside the Event Viewer utility, use the left-hand side menu to select Windows Logs. Then, double click on Application to bring up the Application events in the right-hand side pane.

Inside the Application section, look for an event that states “The following application attempted to veto the shutdown” in the General tab (under the list of events). Since you’ve just forced the warning message to appear, it should be one of the very first listings since the default order is by date/time.

You will be able to find the executable that is causing the warning message. Tell us what it is.

[Britgirl]

This is the log extract which shows the problem with permissions.

These are the only errors that are actually showing:

2959 2959 2024-05-23 15:27:03 985.560 NXSERVER Process initialized with arguments '--virtualsession --sessionid 9C179A65C3D88C951906D21B49D48B78'.
2959 2959 2024-05-23 15:27:04 685.161 NXSERVER Read 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n' 78 from FD#16.
2959 2959 2024-05-23 15:27:04 685.247 NXSERVER Handling connection error 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n'.
2959 2959 2024-05-23 15:27:04 685.409 NXSERVER ERROR! Received error message from node ':', 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n'
3002 3002 2024-05-23 15:27:35 601.923 NXSERVER Process initialized with arguments '--virtualsession --sessionid 2014DAC8AE6D73DF2E5952BC9823277F'.
3002 3002 2024-05-23 15:27:36 242.431 NXSERVER Read 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n' 78 from FD#16.
3002 3002 2024-05-23 15:27:36 242.490 NXSERVER Handling connection error 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n'.
3002 3002 2024-05-23 15:27:36 242.659 NXSERVER ERROR! Received error message from node ':', 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n'
3045 3045 2024-05-23 15:28:07 166.900 NXSERVER Process initialized with arguments '--virtualsession --sessionid 7575FB0F58880F0183A9C512A67CDAB7'.
3045 3045 2024-05-23 15:28:07 841.607 NXSERVER Read 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n' 78 from FD#16.
3045 3045 2024-05-23 15:28:07 841.690 NXSERVER Handling connection error 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n'.
3045 3045 2024-05-23 15:28:07 841.894 NXSERVER ERROR! Received error message from node ':', 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n'
3093 3093 2024-05-23 15:28:38 714.884 NXSERVER Process initialized with arguments '--virtualsession --sessionid 42222011AFC14FECB63EB0041331FCD2'.
3093 3093 2024-05-23 15:28:39 406.174 NXSERVER Read 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n' 78 from FD#16.
3093 3093 2024-05-23 15:28:39 406.258 NXSERVER Handling connection error 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n'.
3093 3093 2024-05-23 15:28:39 406.409 NXSERVER ERROR! Received error message from node ':', 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n'
3137 3137 2024-05-23 15:28:49 903.362 NXSERVER Process initialized with arguments '--debug --collect'.

From the logs you sent us it shows that the frame buffer cannot start because of the home directory error.

[Author]

Posts