Forum Replies Created
-
Posts
-
Support for Pipewire in NoMachine was added in v8. So you have two choices:
1) update to version 8. If you update you should also execute the command:
sudo /usr/NX/bin/nxnode –audiosetupOtherwise uninstall v7 completely and install v8.
2) if you don’t want to update, you could also try the workaround which we provided for Ubuntu.
How to enable audio on systems relaying on PipeWire for sound
https://kb.nomachine.com/AR07T01168Hello,
Did you set the option key=”EnableHardwareEncoding” key to 0 in the node.cfg on the server side and there was no change? You could also disable HW encoding (again on the server side) by going to: server settings -> server performance -> uncheck “Use hardware encoding”. Then try connecting again.
If that doesn’t help, next step is to try disabling HW decoding on the client side.
Try the following:
1. Quit the Player and disable hardware decoding in the player.cfg with option key=”Enable hardware accelerated decoding” value=”disabled”. Restart the Player. Try connecting again.
Assuming you have a valid subscription you can also use the official support channel if you prefer which will avoid sensitive information being published here.
Thanks for the additional info. In your earlier topic you mentioned you were using Workstation, so I assume you still are.
Could you tell us if you see any difference in how keyboard is mapped when connecting to 1) virtual NoMachine desktop 2) physical display and 3) tell us if you are connecting to a vnc session already running.
Screenshots show that nxnode is not running and that is why the systray icon is not visible. Can you enabled debug and send us the logs from the affected Windows by opening a CMD console as administrator and running:
> %ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug nxserver --debug --collectWhat was your previous version when you didn’t see this behaviour? There were no changes in the client between 8.2 and 8.3 which could cause this.
You could try cleaning up the user files directory, by closing the client and deleting almost everything in C:\Users\<username>\.nx , but keeping only folders ‘config’ and ‘cache’.
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”.