Forum Replies Created
-
Posts
-
By the way, I noticed you are using an earlier version of the NoMachine player (7.13). Although we maintain compatibility, please consider updating your software to keep the versions aligned 😉
Hi, logs don’t show anything strange.
Please take a look at the article about headless machines and follow the tips there:
Connecting to Linux headless machines with NoMachine
https://kb.nomachine.com/AR03P00973If you are using Wayland, take a look here:
Notes for connections to Linux physical desktops running Wayland
https://kb.nomachine.com/AR02P00969If you continue to have problems, we can take a look at the logs of the server machine with debug enabled. Follow the instructions here for those https://kb.nomachine.com/DT07S00243 and send them to forum[at]nomachine[dot]com using the title of the topic as the subject of your email.
Hi, if the custom script terminates before the time-out and exits with a non-zero code, in that case NoMachine reports an error. If the script finishes with exit code 0 before timeout, then the session is started. If the timeout is reached and the script has still not finished, the script is killed and NoMachine reports an error. What is happening in your case? Can you provide some more details about your script and what you are trying to achieve? Do you need your script to have finished running before the start of the session? Or can it maybe run in the background whilst the session still starts?
The time out for custom scripts is a value (30 secs) which is currently not configurable but we can evaluate the possibility to make it configurable. What would you like to achieve with your script that needs longer?
Here is the Trouble Report link so that you can track the issue.
https://kb.nomachine.com/TR01V11052Hi,
can you tell us the Linux distro that is installed on the Rock Pi? What desktop environment is it? Steps to reproduce?
You mention “login acceptance”, does that mean User 1 accepts the request to connect from User 2? What NoMachine product is running on the Rock device? The free version or the Enterprise Desktop?
Could you submit those logs to us via email? Send to forum[at]nomachine[dot]com. Thanks!
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 🙂
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!
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 --collectSome 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.debIf 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/TR10U11031You 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.
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/AR10K00706Q2. 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/AR01T01151How to enable VirtualGL support on Linux in NoMachine
https://kb.nomachine.com/AR05P00982Why VirtualGL requires access to the display :0
https://kb.nomachine.com/AR12K00764I hope you find this additional info helpful.
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.
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!