Forum Replies Created
-
Posts
-
Hi, what kind of “monitor combinations” have you been trying? 🙂
In any case, depending on the video card and drivers, it’s possible that the GPU is turned off on a headless system, so in that case, screen capture would also be impossible. On previous versions of Gnome that still support(ed) X11, NoMachine would be able to create a virtual display in these specific cases, but this won’t work with the version of Gnome that is present in Ubuntu 26.04. Running pure Wayland virtual desktops will be added in NoMachine 10, so watch out for that. For now you could consider using a different desktop environment or attach a dummy HDMI dongle.
Hi, these logs are not from the server and not the correct logs from the player. Let’s get a complete set:
For the correct player logs, the device you are connecting from, first we must make sure they are not deleted:
Step 1 – Open the UI on the device -> Player Settings -> Security
Step 2 – Enable the option ‘Don’t delete log files on exit’.
Step 3 – Connect and reproduce the problem.
Step 4 – Go to the Player settings again on the device you started the connection from, Player -> Security -> Take logs.
Then you can collect the server side logs, on the machine you are connecting to (https://kb.nomachine.com/DT08U00298#1.1):
Step 4 – Open the UI on that host -> Settings -> Server -> Security
Step 5 – Scroll down the Security panel till the end to find section ‘Server logs’ -> Take logs.
Attach everything here or send direct to forum[at]nomachine[dot]com. Thanks!
Also, can you describe exactly what happens if the “grab the keyboard” option is selected. Does Alt+Tab starts on Windows? Does the Alt+Tab key sequence work on the Mint host as it should?
Hi, we are not able to reproduce. Alt+Tab works when there is grab keyboard enabled from Win11 to Linux Mint 22 with Cinnamon desktop. Can you update to 9.7 and report back? If you are still encountering the issue, logs could be useful (from both sides) after having reproduced the behaviour. You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298
You can attach them here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!Hi, thanks for reporting. We have reproduced the problem and it will be fixed in the next update (post 9.7).
Hi, NoMachine turns on Mouse Keys when it detects that no mouse is attached to the server. We know that this is not ideal, but it’s the only way for NoMachine to be able to show the cursor. In fact, the OS sets an invisible cursor when there is no mouse attached, unless Mouse Keys is enabled. If you don’t have a mouse attached to the server, you could try attaching one.
Hi, right now we don’t have a NoMachine server planned for iOS or Android. PmOS is based on Linux, but we don’t know if NoMachine installs correctly. If your willing to try it, we’d be happy to receive feedback.
Hi, sorry for the delay in coming back to you. Ideally we would need logs with debug enabled to dig deeper. Today, we are going to release 9.7, so what I advise is you update your installation with this new release and if you are still able to reproduce, enable debug (level Debug – 9 in the UI), reproduce and submit new logs.
Hi, on further analysis of the logs, we can see that the issue you were encountering was a minor bug that we reproduced recently and was specifically related to the update of the Enterprise Client package and only when updating through the player. A fix was already released in 9.5, but a fresh install is recommended. Future updates through the player should not be affected.
Hi, thanks for reporting this. We are also testing the preview, and our developers are currently investigating the issue further. As Golden Gate is still in Preview/Beta, there may be additional updates from Apple that could affect or change this unexpected behaviour. In any case, thanks again for flagging it, we’ll keep investigating and share any updates here.
Hi, thanks for reporting this. We are also testing the preview, and our developers are currently investigating the issue further. As Golden Gate is still in Preview/Beta, there may be additional updates from Apple that could affect or change this unexpected behaviour. In any case, thanks again for flagging it, we’ll keep investigating and share any updates here.
We have tested on the fly to see if we can reproduce and we were not able to. You say “even in”, which would suggest that for you it was broken before (?) Did you already submit a topic or perhaps a support enquiry about this issue? If you submitted a support enquiry through our website, it would be better to continue through that channel, so the support team can link up previous requests with your new report.
Please submit the logs from the Cloud Server after having reproduced the issue. You can gather logs through the UI or from the command line, further instructions are available here: kb.nomachine.com/DT08U00298. Send them to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email. Thanks!
Ah sorry I didn’t provide the link, check here for instructions on how to get the logs: https://kb.nomachine.com/DT08U00298. Let’s get logs from both sides – not just the server, but also the device you are connecting from when you encounter the problem.
Hi Jesse, thanks for your nice feedback 🙂
NoMachine already fully supports CachyOS with Plasma KDE on Wayland. Did you recently try? If you’re experiencing problems with the latest NoMachine version, send us the logs.
Regarding your question about desktop scaling, do you use Linux on both server and client side? Is the client using 200% desktop scaling or the server? Can you show us the problem with a screenshot or describe in more detail?
Hi, so it’s a drivers-related problem. It could have been caused by a drivers update since the last time you used NoMachine maybe? Maybe there is a more recent update that you can try?
Please tell us:
- graphics card model
- version of the drivers
- a screenshot (or a video) showing the screen tearing (you’ll have to re-enable HW decoding again)
- client side logs taken while reproducing the issue (during the session > Ctrl-Alt-O > Connection > Take the Logs)
You can attach them here or send directly to forum[at]nomachine[dot]com.