Forum Replies Created
-
Posts
-
The recent version didn’t change anything which could affect how NoMachine connects to remote Windows (headless and non).
Try these settings, by adding them one at a time to the node.cfg on the Windows computer you are connecting to.
First add
DisplayServerExtraOptions "-displayrequired"and start a session. If that doesn’t improve, add
DisplayServerExtraOptions "-nodxgrab -nodxgigrab"regardless of what I use to connect to it
So it’s something affecting every remote access tool you choose 🙂 not just NoMachine?
If that GPU doesn’t work normally when monitor is powered off, it’s possible that there is nothing we can do.Hi, we are aware of this and have opened a Trouble Report which you can monitor here:
https://kb.nomachine.com/TR10T10632The fix is planned for the next maintenance.
Hi 🙂
something similar was reported by another user here:
https://forums.nomachine.com/topic/issues-connecting-to-manjaro-kde-plasma
which is being caused by the nvidia drivers and not by NoMachine. Can you try disabling HW decoding on the Player machine?
Edit the file $HOME/.nx/config/player.cfg and set the configuration key “Enable hardware accelerated decoding” to “disabled”.
Before changing the configuration key, you should first quit the NoMachine Player (you can do this by right clicking on the !M icon in the system tray and selecting ‘Quit NoMachine Player’.
Then re-open the Player and connect again.Another thread on our forums also reports more about the cause:
Hi Dammé,
can you send the log files/attachments that didn’t upload to forum[at]nomachine[dot]com? Use the title of this topic as the subject of your email. Thanks 🙂
Hi, it looks similar to another topic https://forums.nomachine.com/topic/issues-connecting-to-manjaro-kde-plasma. In that case, disabling hardware decoding on the client side helped.
We would be interested in seeing the backtrace of the ACER box to make sure. Can you check for segfaults on the Player side? This article explains how to look for core files, https://kb.nomachine.com/AR09L00810.
After that, in the Player computer, please edit option key=”Enable hardware accelerated decoding” value=”disabled” in player.cfg. Before changing the configuration key, you should first quit the NoMachine Player (you can do this by right clicking on the !M icon in the system tray and selecting ‘Quit NoMachine Player’. Then try to connect from your ACER client again.
After setting this key
option key="Enable hardware accelerated decoding" value="disabled"did the problem go away?There was a typo in my tip for Fedora, sorry, it’s corrected now. I meant to write this: set the option key=”EnableHardwareEncoding” to 0 (zero) in node.cfg on the server side
Hi Branden,
we’re working heavily on this. It’s due in a few weeks, as well as the iOS version. The problem was the GREAT development work on the 8, that took, basically, all our resources.
Stay tuned 🙂
Now that version 8 for Windows, macOS and Linux is out, our developers are working hard to bring you the mobile update (ios and Android) as part of v8’s early maintenance releases moving forward. This is our priority now. The new update for iOS will fix a number of outstanding issues that are reported in the NoMachine for Mobile forum and in the Apple store, including the more recent issue of the NoMachine app no longer being compatible with iOS 16.
Hi,
you have to uninstall one first then reinstall the other.
That is correct, by design. On Windows, 32-bit is installed in “Program File (x32)” and x64 is installed in “Program Files”.
practical/measured differences between the two, aka if it’ll be worth my time swapping over?
The NoMachine packages offer exactly the same features and functionality.
Hi, cj1171 and jm76430, we’d like to send you a binary which would allow us to gather some additional data. We can send you further instructions via email if you agree.
To tbrown405, this could be a different issue altogether. We’ll come back to you 🙂
No. You have different users exactly for this kind of problem 😉 Customizing gsettings is a question for Gnome/CentOS developers maybe?
It’s hard to know. Your logs didn’t show anything unusual and we also didn’t change add or fix anything in the latest release that would lead us to believe that it could have been related. We weren’t even able to reproduce the same problem that users here have described. But I’m glad it’s solved for you 🙂