Forum Replies Created
-
Posts
-
We are investigating. Thanks for the additional information about v8 working well. Are you able to submit those logs to us anyway? They would be useful to us because so far we’ve been unable to reproduce the problem. Please enable debug (level 9) on the NoMachine server host, restart, then reproduce the issue. Also, you mentioned earlier that you install roles and features, can you give us some more information about that? Are you using default roles or are you creating user permission groups and adding some users automatically there?
Hi,
send the logs to forum[at]nomachine[dot]com. Use the title of your topic as the subject of your email. Thanks 🙂Hi, from what you write and show, it looks like the root window resized, but the desktop ignored it. Can you try enabling the button “Resize remote display” in the Display menu (in the session, Ctrl-Alt-0, Display)? Does that help?
If that doesn’t help, please tell us the server OS and version. Also the NoMachine product you have installed on the server side.
Hi, yes we got them. We’ll come back to you soon. Was the workaround in the topic that I linked earlier not effective?
We’d like to send you a debug package which will allow us to extract more detailed logs. If you’re interested, let us know and we’ll send you further instructions.
No. With Filevault enabled, you have encrypted your disk which means that to allow NoMachine to connect to the screen there, it has to be decrypted first. Indeed, the macOS dialog for the password to de/encrypt the disk looks very similar to the login screen.
Are you using Cosmic? This could be related to https://forum.nomachine.com/topic/pop_os-24-04-cosmic-desktop-white-screen. So please try the workaround indicated there.
Additionally, we would need to see the full logs from the PopOS host so that we can confirm what’s causing the error. You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298. Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Hello,
thanks for the client side logs. We would also need details of the machine you are connecting to:
– OS version
– if Linux, the distribution and version
– NoMachine server versionand the steps to reproduce the problem.
Please submit the logs from the server host you are connecting to. You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298.
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Can you provide the output of the following commands?
gdbus call --session --dest org.gnome.Mutter.DisplayConfig --object-path /org/gnome/Mutter/DisplayConfig --method org.gnome.Mutter.DisplayConfig.GetCurrentStategdbus call --session --dest org.gnome.Mutter.DisplayConfig --object-path /org/gnome/Mutter/DisplayConfig --method org.gnome.Mutter.DisplayConfig.GetResourcesIf you try the package we sent you (remove your workaround first), do you still reproduce the black screen?
Hi, we have a special debug package that we’d like you to try. If the black screen continues, we will need logs from the macOS server host. I will send his via email with further instructions.
Hi, we have a Trouble Report open which is similar to what you are describing. Can you please try the workaround that is described here: https://kb.nomachine.com/TR05W11320. Does that help?
Hello, the problem you are encountering is most likely being caused by something else. Can you confirm the exact steps to reproduce the problem? Are you using multi-monitors? Also, a full set of logs which you can attach here (https://kb.nomachine.com/DT08U00298#1.1) or send directly to forum[at]nomachine[dot]com. If you choose to send via email, please use the title of this topic as the subject. Thanks!