Forum Replies Created
-
Posts
-
All’s well that ends well! 😀 Kidding aside though, there must be a reason somehow connected to your ssh tools and I would not exclude that it’ll happen again in future. We’re here to assist you in that case. Long live the keys!
For some reasons, the key attached to the post is not valid, I’m getting these outputs when testing it with openssh 9.6p1
ssh-keygen -l -f testkeyfornomachine 256 SHA256:eWl6FVVBI16fflrvux+rY0JgcV0bQmeKaTdktJi0RGQ “TestKeyForNoMachine” (ED25519) ssh-keygen -y -f testkeyfornomachine Load key "testkeyfornomachine": invalid formatIf you run the same commands on your end, do you get anything different?
While editing the Trouble Report with the recommendation submitted by @neatchee I noticed that there are some additional questions we can ask to collect details for the debugging, so here they are:
- Besides the key type security concerns, we assumed that the RSA key login is still working correctly. Could we get a confirmation?
- Where are the ED25519 and ECDSA key files located on disk? Did you maybe try to move them in different system folders (e.g. $HOME, tmp/, .nx/) to verify if anything changes?
- Are key access permissions correct, so both folder and file can be accessed by the user starting the player process?
- Can you share any of the key pairs not working, so we can test them in our labs? You can contact us at forum[at]nomachine[dot]com.
Thank you for helping us to debug this mysterious issue!
Interesting, process could not even create the logs directory. Please run the command
/usr/NX/bin/nxplayer --log stderrin a terminal, let me know what you see there as output.Usually aborts are tracked also in client logs, so we’ve a good chance to find useful hints there. Could you pack your
$HOME/.nxfolder and send it to forum[at]nomachine[dot]com, please?Hi. There are no known issues like the one you’re experiencing, so we can troubleshoot it together by starting from a check of
journalctl, it will help to verify if the client is segfaulting. Try to start it, then runjournalctl -rand check if the processnxplayer.binwas closed because of a segfault. Copy the line and paste it here in the thread.Hi. Are you using the touch or the pointer mode? Is the issue occurring in both cases? Can you try to open Display settings and enable the viewport mode, then verify if taps are correctly interacting with the desktop?
Hi biglia.
The version number 10.0.19041 was extracted from the dump you sent, and while we know that Microsoft has unclear rules about the DLL versioning (for example on all our full updated 22H2 machines, ntoskrnl has different versions!), we preferred to suggest to update your machine because this versions mismatch makes it hard to compare systems and detect reasons for different behaviours, most of all when they occur in a deep system layer.
Troubleshooting your problem has been quite painful, as the NoMachine client process is closed before it can start doing anything meaningful: the Workstation Service DLL is loaded in a chain of dependencies and, when trying to do its stuff, raises an exception and causes the process to terminate. The exception description is “The network address is invalid”, and there is nothing the client did up there to cause an error like that.
After all our attempts to reproduce the issue and to progress in the debug through static analysis, we can certainly say that this problem is completely out of our control. A possible reason why it happens with NoMachine only (at least from what you’ve seen so far) is the sequence of DLLs loaded that badly interact with one or more configurations and third party services on your machine.
We tried to replicate your environment with WSL and WSL2, by publishing and accessing multiple resources on the network to extensively use Workstation Service, but we never succeeded to reproduce the same issue.
I remember you said that one of your machines with the same configuration works correctly. You could try to compare the services and configurations, and check event viewer to look for anything useful about wkscli. As of WSL, a good starting point could be the issue tracker on github. If you’ll find anything that you think valuable to be shared, we’ll be happy to know it. 🙂
Do you need that the client machine runs also the server? If you do not, please try to shutdown and disable the server (Quit NoMachine service from the tray menu, choose to not start it again) and verify if the configuration is correctly moved.
Some questions:
1. What do you mean with “server client” and “player client”?
2. Where are you changing the default path for logs, on client, on server, or both?
3. What is the product you’re using on client and on server?
4. How do you launch the client?Hi. You should be sure that the location is accessible when the client is launched, in the contrary case the default location will be restored.
Hi. Can you send the output of the command
setxkbmap -printexecuted in a terminal window on Ubuntu? Are you connecting to the default Ubuntu session, or you’ve started an additional X server (like Xvfb)?Hi. From the logs you submitted it seems the problem is occurring on the server, which is closing the connection almost immediately. Could you get server side logs please? They’re in
%ALLUSERSPROFILE%\NoMachine\var\log, if they’re too big you can send them to forum[at]nomachine[dot]com.Hi. Interesting device! Do you see a crisp display image through glasses? Are they tiring? Thank you for sharing your experience.
About the problems you noticed, I’m going to give you some info and how we plan to work on them.
1/3. This is something annoying because Android (at least up to version 14) doesn’t give a way to easily remap its shortcuts, like Win/Super, Alt+Tab, Alt+F4, etc. We’re running some experiments by installing a service using the accessibility layer, so far they’re promising but we’ll have to evaluate how to pack the service with the application because it is a pretty sensitive privacy layer.
2. Unfortunately we can’t help for this, as the actual pressed key depends from the keycode got from the input device (your Seenda keyboard, in our case). You could try to look for ways to lock the Function key, for example one of Seenda keyboard models can lock it by pressing Function and Delete keys. The solution for this has to be searched on device/OS side.
4. We’re adding to DeX the fullscreen mode working just like the desktop application, with a button or shortcut allowing to switch from window to immersive fullscreen mode. Nothing more to add about this, we’ve started working on it after your report and I don’t expect problems.
5. I can confirm what Britgirl said, it is a known problem and we’ll release a fix in our next release.In the end, you could temporarily use the workarounds you proposed, until our next version is shipped.