Forum Replies Created
-
Posts
-
Please try disabling hardware decoding on the Windows client.
You can disable it completely in the player.cfg. Please edit the file$HOME/.nx/config/player.cfgand set the configuration key “Enable hardware accelerated decoding” to “disabled”.I understand that the computer you are connecting from is Windows 10. What NoMachine product installed on the server side? Are you the administrator of that machine? What OS is the server side?
Hi Holly, this sounds like you need to configure your home router for external access. See this article for the explanation and further tips:
How to connect to NoMachine when the server is behind a NAT router or a firewall
https://www.nomachine.com/AR11L00827We aren’t aware of issues with disabling the !M icon and notifications. We checked on the fly to make sure. When changing either of those keys, you need to restart the machine. Did you restart? The player also has a service icon which becomes visible when you open NoMachine, to start a connection for example. See 3.3. Quit NoMachine Player in the Connection Monitor Guide: https://knowledgebase.nomachine.com/DT11R00202#3.3
Balloon messages, which are used to notify (e.g someone has connected/disconnected) as well as prompt the desktop user to accept a specific function (e.g accept an incoming connection), are a central security feature of NoMachine software. You should know that whilst in version 7 it is possible to disable all balloon messages using the appropriate key in node.cfg, in version 8 the disabling of all balloon messages will no longer be possible.
In the next major we have maintained the possibility to show/not show the !M service icon in the system tray (like it is in version 7) but notification messages will still be displayed since they are independent from the !M icon. We will see in the future which notifications will be possible to disable on an individual basis, but to disable all will not be an option, as I said, for security reasons.
Consider using an alternative distribution, perhaps Ubuntu? It seems popOS can’t work with Pulseaudio
https://www.linuxquestions.org/questions/showthread.php?p=6350038
or wait and see if popOS developers fix the issue.
Yes, it can.
From a terminal you can check with
nxserver --useredit USERNAME --screensharing yes. This applies to a specific user.
Also, in the server.cfg check that PhysicalDesktopSharing is set to ‘1’. This key applies to the whole server. Does this help?Just a note about this behaviour in version 8, the risk of being locked out because the “desktop shared” button was toggled to off before logging out will be mitigated: the owner will still be able to connect even if the desktop is set to “not shared”.
We aren’t aware of copy and paste issues between Fedora/Windows, or working one way only.
Are you using Wayland, and what DE is installed there?
PopOs is ubuntu-based I believe, so try with
sudo apt install -y pulseaudio.The FR you linked is specific to Fedora. We will be extending support for Pipewire across the supported Linux distros.
Hi, indeed a fix was applied in this package, but we needed you to test it in situ so that we could monitor it if it were to happen again. That both of you say the problem has gone is good news. This fix will be officially added to the next release. Thanks everyone for your cooperation!
We already knew that the Pulseaudio was going to be dropped, we just weren’t sure when 🙂 Thanks for submitting the link to the news!
Thanks for letting us know.
Just as a side note for all Raspberry users, you can consult the article in our knowledge base which outlines which packages you should install depending on the architecture of your RPi.
Installation & configuration notes for NoMachine Linux Raspberry Pi packages
https://knowledgebase.nomachine.com/AR07N00896Quoting said article: To check what architecture your Raspberry based on, open a terminal on your device and run the uname -m command. Some examples:
armv6l – means that you should useARMv6 packages
armv7l – means that you should use ARMv7 packages
aarch64 – means that you should use ARMv8 packages