Forum Replies Created
-
Posts
-
Logs show that Wayland is enabled. Please make sure that Wayland is disabled, reproduce the problem and submit brand new logs.
Hi, the screenshot didn’t attach, can you submit it to forum[at]nomachine[dot]com and we will upload it to your topic. Thanks.
It looks related to this Trouble Report:
White screen occurs when connecting to a KDE/Plasma Wayland desktop on Kubuntu
https://kb.nomachine.com/TR07U10921Try disabling Wayland and using X.org instead. Does that help?
We are producing a similar behaviour and it seems to be caused by a recent nvidia drivers update. You have version 545 (libnvidia-encode.so.545.29.06). Can you downgrade to 535 and tell us if the problem disappears?
Before you downgrade to try, please send us the logs from the NoMachine server. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. Send them directly to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email. Thanks!
We have checked MX Linux and have not been able to reproduce any similar behaviour. It would have been useful to know the desktop envirionment on the MX Linux system. It could well be x.org crashing. What’s not clear is your setup. Are you are using MX Linux on the Raspberry or are you using a MX Linux NoMachine client to connect to the Raspberry? If the latter, what is the OS and desktop env is on the Raspberry? If you wish for us to investigate further, please provide us with the full set of NoMachine logs as requested from client and server sides? (link in previous reply).
edit: in your case, using Wayland instead of X.org could help.
Hi, do you have a second monitor attached to the M1 laptop? We can reproduce this behaviour if another monitor is attached to the laptop. If this is not your case, please describe precise steps to reproduce.
Hi, we will be adding a timeout parameter to the scripts. This will allow you to set a timeout that fits your custom script setup.
so for example,
UserScriptAfterLogin "/usr/script/afterLogin.sh --timeout 180.This will be implemented for version 9.
The most reasonable implementation would be to send a WOL packet just before the connection attempt, so that if the server is not running, it would restart its run, or send the WOL packet if the server is not immediately responding in a reasonable time, like a couple of seconds. The WOL packet, instead, is now sent after the connection timeout, if the remote host is not responding. The reason it was done like this was to overcome a few WOL problems and incompatibilities we encountered at the time of the first implementation. We actually retested all of this and it doesn’t seem that these problems and incompatibilities still hold. This means that a more reasonable implementation should come shortly, actually resolving the problem you detected. Thanks for reporting.
I’m assuming you’ve got the free edition installed on the Windows 11 PC. A NoMachine Free Edition installation will accept 1 connection. If you’ve started a connection to your Windows 11 PC and then start a second connection to the same PC, the first connection will close. Two NoMachine players connecting to the same Windows desktop requires Enterprise Desktop.
https://www.nomachine.com/product&p=NoMachine%20Enterprise%20Desktop
Not quite sure what to make of what you wrote. With HW encoding/decoding enabled, then NoMachine uses the graphics card available on the host in order to encode or decode. If that’s not possible, NoMachine reverts to H.264 software encoding. This is explained in the material that I pointed to.
As for hypervisor technologies, NoMachine works out-of-the-box with most of them and we test with quite a few including Proxmox.
NoMachine can be used with VOIP applications in the following scenario https://forum.nomachine.com/topic/audio-from-user-to-user#post-41572
Hi, can you submit all attachments and images to forum[at]nomachine[dot]com? Also confirm distro and version on the server side and what OS you are connecting from. Desktop env will be useful as well.
I had in mind that NoMachine was able to adapt the remote resolution as the client window is resized.
It does 🙂 provided the following conditions are met:
When the connection is to the physical desktop (any OS) , the supported resolutions are those of the remote graphics card as listed in the System settings on the server. The session resolution on the client side cannot be higher than the maximum resolution supported by the remote graphics card (server side).
The supported resolution for virtual NoMachine desktop sessions (Terminal Server for Linux products) doesn’t depend on the remote hardware and thus the remote screen can be resized to whichever resolution is supported by the user’s local monitor.
I pasted this text from the article here:
Some tips about resize and scaling options for NoMachine remote desktop software
https://kb.nomachine.com/AR02M00835