Forum Replies Created
-
Posts
-
I was just about to answer you when you posted a reply. Anyway, if it can help, we have this article:
https://www.nomachine.com/AR08M00857 for trouble-shooting.We also generally recommend not to have another NX-derivative on the same server as NoMachine as we cannot guarantee that there won’t be incompatibilities.
The issue you encounter is known and will be fixed in the next mobile release v8.
No sound on headphones connected via bluetooth on iOS
https://kb.nomachine.com/TR10P08884The server-side logs are not complete, so we are unable to provide a diagnosis.
Please update to 8.3.1, the latest version, both sides. Then
Run
/etc/NX/nxserver --debug --enable on the server.Then
/etc/NX/nxserver --restartThen reproduce the issue, and then run
/etc/NX/nxserver --debug --collectIt will create .zip with node logs. Share this file with us via email. Thanks!
We’ve not encountered this during tests. We’ve tried several times without success. About your question regarding “graphics”, do you mean copy and paste of graphics won’t work? Copy and paste of images is not supported. You can transfer images by zipping them up and either using the file-transfer feature or dragging and dropping. (so if you are trying to copy a small image of your text, this is the reason for the error).
however now my connection to the remote machine is incredibly laggy. The mouse takes several minutes to move or respond.
It’s strange that lagginess would be caused by disabling hardware acceleration (which would mean falling back to software acceleration). Did you send us the Player logs as requested? Tick the box “Don’t delete logs on exit” in Security of the Player settings. Start a session, reproduce the behaviour and submit them as before.
Of course 🙂
See this topic https://forums.nomachine.com/topic/how-do-i-get-the-help-screens-back for more details.
Hi,
had never experienced this before when using older versions of NoMachine and macOS, but now that I have upgraded my macOS and upgraded my version of NoMachine and now I have these sleep-related connectivity issues.
If the Mac is sleeping, then it’s normal that NoMachine is not broadcasting itself on mDNS. Can you tell us what macOS version you are using now? Are you now using 8.3?
If you configure the system to use Wayland on the physical desktop, connections to the physical desktop should work.
If you have a headless or you want to use a virtual display, there will be some issues as explained in our article here:
https://kb.nomachine.com/AR02P00969 section “Known limitations”.
Can you try disabling client-side image post-processing. Start a connection, open the menu Ctrl-Alt-0 -> Display settings -> Modify -> tick the box ‘Disable client-side image post-processing’.
https://kb.nomachine.com/DT09T00266#5.8
From the above guide “This is useful if the client-side device has low processing power, or too much CPU is being used to decode, disabling this can help.”
Is there a setting to always hide the local cursor?
No, hiding the local cursor is not possible. There is also not an option to change the local cursor to a dot when you are in the session window.
This is not something we have encountered in our labs. Testing on the fly we can confirm that on Ubuntu 22.10, everything works out of the box with default manufacturer settings, so we have not idea what you could be doing wrong.
What you didn’t mention is what desktop environment you have on these hosts, what display server is it (Wayland or Xorg?) and the typical steps to reproduce this problem. For example, you say that it happens when the connection has been interrupted for some reason or another: what is the reason for the “interruption”?
What errors, if any, does NoMachine show when you try to reconnect after this interruption?
Logs of the server side would also be useful so we can check what is happening. Follow the instructions in the document here and then send them to forum[at]nomachine[dot]com
https://kb.nomachine.com/DT11R00182. Make sure you enable debug first, reproduce the problem and then extract the logs.
Thank you.
I’m not sure what you mean. Perhaps you could describe the steps you are taking?
Anyway, we reproduced the error reported by the author of this topic and you cant track it here:
What is your desktop environment? Wayland or Xorg?
Some tips for Wayland environments are here:
Notes for connections to Linux physical desktops running Wayland
https://kb.nomachine.com/AR02P00969