Forum Replies Created
-
Posts
-
Thanks Cytan299 for the update. That’s good to know.
IndianaM1ke, can you update your macOS like Cytan299 did and tell us if the issue is resolved for you?
Sorry for not updating you. We have been trying to reproduce the error using your exact set-up and steps but without much luck. However, there is a TR already open on a similar issue related to Windows client connecting to Gnome, upon using the Right-Ctrl + Shift + V in the session, it toggles the control key press. It might be related to this. Can you check if the workaround can help in your case?
We need to clarify better what is the client OS you are using to connect from and what is the server OS host you are connecting to when you encounter this issue. You mentioned that you turned hardware encoding off on the Ubuntu client. HW encoding is turned off on the server. On which Ubuntu machine did you disable HW encoding?
We understand that you are connecting from the macOS or Ubuntu 24.04 (clients) to the Ubuntu 22.04 server? Is this right?
Is it only when you connect from Ubuntu 24.04 to the Ubuntu 22.04 server that you have this problem? If so, you could try disabling hardware decoding on the Ubuntu 24.04 client. To do this follow the instructions here https://kb.nomachine.com/AR07U01202 making sure to set the option key=”Enable hardware accelerated decoding” to value=”disabled”.
Hi, thanks for your feedback. NoMachine is a commercial software but we do release some components to the public, and you can find them here: https://downloads.nomachine.com/opensource/. Indeed, hardware encoding on ARM is not currently supported in NoMachine. It is planned though! Other features coming in version 9 were prioritized, but it is definitely something we are going to add.
Hi, unfortunately there is no other alternative workaround other than using X11, but if you send us the server side logs, we can check to see what the problem is with the other capture methods? Send them to forum[at]nomachine[dot]com. The instructions are the same as before 🙂 https://kb.nomachine.com/DT07S00243, steps 1, 2 and 3 for the server machine you are connecting to.
Also useful to know:
i) Is the server running in a VM?
ii) Are you using proprietary drivers? If you are, can you possibly try the open source ones?
There is another topic with a workaround, can you try it?
This looks like the following known issue with Plasma 6, https://kb.nomachine.com/TR05V11141.
Hi, can you try disabling hardware decoding on the client machine that you are connecting from? See the article for further instructions making sure to set the appropriate key to “disabled”.
How to disable hardware decoding on the client side
https://kb.nomachine.com/AR07U01202Can you send us the client side logs (the device that you are connecting from)? Please take a look at step 4 in the instructions here, https://kb.nomachine.com/DT07S00243. We don’t need server side logs for the moment.
Hi,
We have planned to add an option to capture the screen of the server at native pixel resolution on High-DPI displays as well as make the NoMachine User Interface “DPI Aware”.
You don’t mention what OS you are using butif you are using Windows, a possible workaround is to
– Right-click the NoMachine app shortcut on your desktop and select Properties
– Select the Compatibility tab
– Click “Change high DPI settings”
– Check the box “Override high DPI scaling behavior”
– Select “Application” from the combo under “Scaling performed by”Hi, changing a label in your Machines panel, changes the name for you, not other users. With MDNS connections, NoMachine broadcasts the presence of the machine and uses the name set on the system. This type of connection (MDNS) works differently to a traditional connection which has its own connection file. If you want others to see the new name, you could change the hostname in the machine’s system configuration. Alternatively, you could create a connection file and distribute that to all your users and they will then also know the new name.
Hi, can you try disabling hardware decoding on the client machine that you are connecting from? See the article for further instructions making sure to set the appropriate key to “disabled”.
How to disable hardware decoding on the client side
https://kb.nomachine.com/AR07U01202Documentation is current but we will certainly check again to make sure everything is up-to-date. About the limitation, I believe I already pointed you to a Trouble Report which explains that there is bug preventing web sessions from using 4096-bit keys for authentication. Here is the link again: https://kb.nomachine.com/TR08Q09394. Developers are currently working on a possible fix.