Britgirl

[Britgirl]

So, workarounds are either to disable Wayland or enable autologin.

[Britgirl]

Can you send the zip file to forum[at]nomachine[dot]com please? Use the title of this topic as the subject of your email 🙂

[Britgirl]

Hi to both of you

we are aware of a similar issue. Logs from affected servers we have checked show the wrong behaviour is triggered someway by Wayland, our developers are looking for a possible solution, but in the meantime the suggested workaround is to disable Wayland.

If disabling Wayland has no effect, please submit logs from the Ubuntu server side.  You can extract them using the instructions here: 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]

Just checked them on the fly. The agent logs are missing 🙁

Can you reproduce and resubmit? From a terminal,
$ sudo /etc/NX/nxserver --debug --enable all (in case you disabled debug already)
$ sudo /etc/NX/nxserver --debug --collect

[Britgirl]

Logs received 🙂

[Britgirl]

Some feedback about this – in checking the latest image of Raspberry Pi OSarmv7 (Bookworm), there is a 64-bit kernel. This is why uname -m command shows aarch64. However, the libraries in Bookwork are for armv7 and that’s why you need to install a package for armv7. So the folks at Raspberry will probably need to fix this in a later update.

On normal systems or older Raspberry devices we block the installation, like here:

sudo dpkg -i /tmp/nomachine_8.10.1_1_arm64.deb
dpkg: error processing archive /tmp/nomachine_8.10.1_1_arm64.deb (–install):
package architecture (arm64) does not match system (armhf)
Errors were encountered while processing: /tmp/nomachine_8.10.1_1_arm64.deb

If you are running Wayland, please use X.org instead. There is a Trouble Report already open which you can track using this link:

Wayland doesn’t work on Raspberry boards
https://kb.nomachine.com/TR10U11031

[Britgirl]

You are right that Buster is outdated, and this information will be updated. We are currently making changes to the website in general, including the download pages which should facilitate finding the right packages. These modifications to the website are planned for the release of v9 of the software, but in the meantime the current website can of course be updated with more recent OS information.

How did you come up with that link?

The link is available from the main page for Raspberry (not sure why you were not able to find it).

Click NoMachine for Raspberry in the menu which takes you here: https://downloads.nomachine.com/linux/?id=29&distro=Raspberry

Then select “NoMachine for Raspberry ARMv7 DEB”, under Raspberry Pi 4.

NoMachine should block the installation if you are installing an incompatible package (in your case package for 64-bit kernel being installed on 32-bit system), so we are checking what can be improved on our side.

[Britgirl]

Hi.

Q1. How does the hardware acceleration support compares in Windows vs Linux?

Hardware encoding is available in NoMachine sessions in all of the supported operating systems provided the graphics card supports it. It’s available in the free and commercial products.

More about GPU acceleration, H.264 encoding and decoding in NoMachine software is available here:

H.264 hardware and software encoding/decoding in NoMachine remote desktop sessions
https://kb.nomachine.com/AR10K00706

Q2. Are there differences between the free and commercial versions of the software in terms of “hardware acceleration” / “hardware encoding” / VirtualGL GPU access ?

There are no differences in the free and commercial version when it comes to GPU/hardware acceleration/encoding/decoding. Check the article I mentioned before.

However, VirtualGL support and GPU acceleration/HW encoding support are not the same. Whilst the latter is for leveraging the capabilities of the GPU available out-of-the-box to accelerate the encoding of NoMachine, VirtualGL is used to allow OpenGL applications running on NoMachine Terminal Server in NoMachine “virtual desktop sessions” to use server side graphics hardware installed on the application server. VirtualGL is a tool giving your OpenGL applications the ability to run with hardware acceleration even if they are using an X11 display that doesn’t have those capabilities. The VirtualGL library redirects the 3D primitives to capable graphics hardware so that OpenGL is rendered through the GPU if present rather than by software rendering. VirtualGL is a feature you can enable if you have a NoMachine Terminal Server product installed on your Linux machine.

More about VirtualGL is available here:

How rendering of applications is done in NoMachine
https://kb.nomachine.com/AR01T01151

How to enable VirtualGL support on Linux in NoMachine
https://kb.nomachine.com/AR05P00982

Why VirtualGL requires access to the display :0
https://kb.nomachine.com/AR12K00764

I hope you find this additional info helpful.

[Britgirl]

Thanks for letting us know.

If you need to hide what’s on the screen, you can enable screen blanking in the Security section of the Server Settings.

[Britgirl]

Are you able to send us the server-side logs? You can extract them using the instructions here: 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]

Hi, are you able to send us the server-side logs so we can check to see if it’s an already known issue? You can extract them using the instructions here: 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]

Hi, what you can try is installing the armhf packages rather than the aarch64 specific ones. Try the packages here and let us know: https://downloads.nomachine.com/download/?id=106&distro=Raspberry&hw=Pi4

[Britgirl]

Hi there! Thanks for your feedback. Just so it’s clear why there is that “removed” there, we remove all mentions (positive and negative) of competing products, so we can stay as neutral as possible 😉

So we can investigate, we need to have a clear picture of how you are using NoMachine and what you are seeing/experiencing.

Can you send us a video showing problem #1?  (you can send this to our email forum[at]nomachine[dot]com if you prefer).
Can you tell us if the remote PC (the NoMachine server) is headless (no monitor attached) or if it’s a laptop with the lid closed?
Can you tell us whether problem #2 occurs with every game? If if it occurs with a specific game, which game is it?

[Britgirl]

Nan, interesting. Are you able to send us the logs before and after having changed the WaylandModes key? To get logs check the instructions here: https://kb.nomachine.com/DT07S00243. You can send them to forum[at]nomachine[dot]com.

Also, you mention that when connecting from an iPad to the RPi5 and using FreeCAD, those particular keys (shift, control, option) are not working. Are you able to verify if those keys are not working in other applications?

[Britgirl]

So we’ll need to evaluate carefully how to handle it. Anything related to setting a different color space is something complex to be evaluated on multiple hardware specs. Thanks for reporting.

[Author]

Posts