Forum Replies Created
-
Posts
-
We have not been able to reproduce this problem despite several attempts.
Could you please send us the logs from both the player and server sides? Please follow the instructions in the following document for your OS.
https://kb.nomachine.com/DT07S00244
And then send them to forum[at]nomachine[dot]com using the title of this topic as the subject of your email. Thanks.
A quick update on this. We were never able to reproduce it.
Maybe autostart was inadvertently disabled. Something to bear in mind is that in the Free Edition there are 3 services that need to be started, with Enterprise Desktop there are 4:
/cygdrive/c/ProgramData/NoMachine/nxserver/nxserver.exe –startmode
NX> 807 Service NoMachine status is: Automatic
NX> 807 Service NXD status is: Automatic
NX> 807 Service NXHTD status is: Automatic
NX> 807 Service NXSSHD status is: AutomaticThis topic can be considered closed. If the issue comes back, please open a new topic.
Switching to Xorg will help. We reproduced the problem when Wayland is set as the display server.
You can monitor the Trouble Report here:
Hi Nedss, have you updated the iOS app to the latest version that we released recently? Is the problem still there?
If so, can you tell us the external keyboard you are using? macOS version on the server side would also be useful to allow us to try and reproduce.
Apologies for not getting back to you. The first releases of v9 will be dedicated to Network. Development of the feature you are interested in will start after that, so whilst it’s possible that it will be in one of the releases of the v9 branch, we are not able to give you an ETA at the moment. If we have pre-release packages for you to try out, we’ll be in touch with you 🙂
Can you submit a screenshot of the Display settings panel of the NoMachine session menu?
Also, from the server side, a screenshot of the Display settings window of the operating system.
We would need to see logs to understand why you cannot connect. Specific version of Ubuntu and your desktop environment. Are you running Wayland or X.org as the display server?
Please follow the instructions here and send them as an attachment to forum[at]nomachine[dot]com. Thanks.
https://kb.nomachine.com/DT07S00243
Sorry to interrupt. Just send all your attachments to forum[at]nomachine[dot]com. Make sure you use the title of this topic as the subject of your email. Thanks!
What is the desktop environment of the physical display?
What is the desktop environment that you are seeing when you connect?
Assuming you have installed the free version, the free version of NoMachine will start its own virtual display server if it cannot find one, such as when a Linux machine is headless (no monitor attached). See more details about this here: https://kb.nomachine.com/AR10K00700
Meanwhile, when I shut down the computer, it is shown that a new user with same name is added.
What do you mean?
some Python GUI lib can not work on the new virtual display.
What do you mean?
Submitting screenshots would be useful to illustrate what the problem is.
Is it one specific application or any application? If the former, can you tell us what application you are copying and pasting from?
Hi, we are regular users of Proxmox in our labs and we have not come across disconnects as you’ve described.
When you connect from other client machines, do you see an error message of some sort? Can you show us the dialog that you see when you get disconnected?
Can you send us the logs of the client and server sides? See the following article for further instructions: https://kb.nomachine.com/DT11R00181.
You can submit them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
They didn’t reveal anything useful either.
So to sum up: the NoMachine logs don’t show anything strange (just a couple of restarts) and the system logs didn’t show anything that could suggest reasons for a crash.
So, either the problem is not there or the logs are not catching it.
All we can suggest is that you keep debug enabled and then should the issue occur, you should collect the logs and then send them in (nomachine player and server, as well as system logs).
A feature is planned which will allow multi-monitors on the server side to be treated as separate windows on the client side. In each of theses separate windows it will be possible to apply all the usual settings, like applying a different scaling factor, resizing the window to any size and placing the window in any desired location. It comes close to what you would like to achieve, in that n in your case, you could keep 2 monitor windows open whilst minimizing the third one.
Unfortunately, we cannot give a definitive ETA. Development priorities are currently on NoMachine Network (www.nomachine.com/network) and v9. Work on the feature you are interested in may start after that.
Can you show us a screenshot of the “Edit connection” panel and the options you have available in the Host field?
What actually happens when you try connecting the IPv6 address? What is the error dialog you receive/see when attempting to connect with the IPv6 address?
If necessary yes, but you’ll have to upload it to a service from which we can download it because it won’t pass our email server.
For your issue, we’d like to see the stack of the nxplayer and also NoMachine logs as well.
For any core files generated by nxplayer, please see https://kb.nomachine.com/AR09L00810.
For the NoMachine logs, on the device you are connecting from:
– launch the NoMachine UI on the user’s computer from Programs or Menu
– click on Settings -> Player -> Security
– check Don’t delete log files on exit option
– Connect to the server and reproduce the problem.
– Compress the user’s home/.nx directory containing logs.
– Send the compressed logs archive to NoMachine Support Team by e-mail.On the server side, please see: https://kb.nomachine.com/DT07S00244#1.1
And then the journalctl from the server side as well.
Also, is your Debian installation in a VM? We have not been able to reproduce any similar behaviour on our Bullseye test set-up.