Forum Replies Created
-
Posts
-
So the steps to follow to “unlock” the ctrl key are the same and we can therefore establish that it’s the same bug. I am unable to provide you with a target release for the fix at this time, but please use that link to the Trouble Report to monitor its status,
I have uninstalled them all, by using right click in the application in directory and “Move to Bin”. But I don’t know if there are any left over bits that might be causing issues.
You need to make sure you have uninstalled the other components correctly. For example, the correct way to uninstall USB Network Gate you should follow the instructions here: https://help.electronic.us/support/solutions/articles/44001312963-usb-network-gate-uninstallation-on-mac#:~:text=To%20completely%20uninstall%20USB%20Network%20Gate%20and%20all,but%20not%20uninstall%20the%20daemon%20and%20drivers%20J
Do not uninstall by moving USB Network Gate.app into the Trash, as this will only remove the GUI, but not uninstall the daemon and drivers (from their website).
So install UNG again, then uninstall the right way following those steps.
To compile nxusb kernel module you have to delete line 1198:
".owner = THIS_MODULE," in "/usr/NX/share/src/nxusb/nxusb-vhci-iocifc.c"and then runsudo makein the same directory as that file.What NoMachine message are you seeing when you connect?
Did you already take a look at the guide here?
https://kb.nomachine.com/AR04S01122 ?Any idea why the flatpak version couldn’t install?
We cannot know. We are not responsible for NoMachine packages that are in repositories which we don’t have strict control of or don’t officially support. That’s why I wrote to always download and use the packages from the NoMachine website.
A feature is already planned which will allow users to switch the CMD and CTRL keys in the User Interface. It will most likely be in one of the later 9 releases.
Thanks for the additional info. Your output shows that it is not a NoMachine issue but that your vainfo command segfaults. Keep hardware decoding disabled and you should be ok.
(PS you might want to make the NoMachine panel that has this info copy-n-paste compatible, instead of me typing it)
We will. Thanks for the suggestion for improvement.
You mentioned “restarted the terminal and get the same warnings again.” Restart is not enough. You need to reboot. If you disable eglcapture and reboot, then “unset LD_PRELOAD” is not needed.
Always use the packages from the NoMachine website because we cannot be responsible for versions of the software that you find in third party repositories. We don’t verify these packages.
What you should do is uninstall the package using your package manager. Something like
flatpak uninstall --delete-data <appid>I imagine. Then come to the NoMachine website and download the right package for your Fedora installation. Then please also check this article specifically for installing on Silverblue: https://kb.nomachine.com/AR03V01225FTyReNIC, strange. What is the output of the command
sudo -l? Execute that command as the user that cannot authenticate. Or alternatively, you can also check withsudo -l -U <username>.So far we have not been successful in understanding the problem of that your specific Win 10 machine. The output you sent us does not help us pinpoint a reason for the player failing to open. We can only assume that is something very specific, but we will continue to experiment in our labs.
Hi,
RSA, ED25519 and ECDSA are all supported, for both NX and SSH connections. The only exception is with web-based sessions where only RSA keytype is supported (web-based sessions are not available in the free version anyway). Are you importing the keys in the NXS files? Does the problem happen when the keys are not imported?