Forum Replies Created
-
Posts
-
We’ve tried with the latest version (NoMachine 8) and can’t reproduce it.
Enabling ‘Grab the keyboard” in the Player settings captures all keys, including the Super/Win key.
See the image in section 2.1 of this document: https://kb.nomachine.com/DT07S00236#2.1. Do you have the box “Grab the keyboard input” checked?
Note however, that if your connection file (.nxs file) shows
<option key="Grab keyboard input" value="false" />, this setting will override your global setting (configured in Player as in the previous document). You can check what’s in the .nxs file by locating it in the directory defined in the ‘Connections and recordings’ field from the Settings -> Player -> Folders panel of the User Interface.We’ve reproduced this issue and opened a Trouble Report. You can monitor its status using the following link:
https://kb.nomachine.com/TR10T10643
Thanks for reporting.
Can you follow the suggestions in our KB article? You need to enable ‘egl capture’ on virtual machines or on machines where there is no Pipewire installed.
Connecting to a Wayland-based desktop running in a Linux virtual machine
https://kb.nomachine.com/AR04R01083We’ve not been able to reproduce. If you are still encountering the issue after updating to NoMachine 8, let us know. We can send you a debug library.
What you reported is not the expected behaviour. A Trouble Report has been opened which you can track here. It will be fixed in one of the next maintenance releases.
https://www.nomachine.com/TR10T10648
iOS users following this topic please read here: https://forums.nomachine.com/topic/important-notice-for-nomachine-users-about-ios-version-16
Furthermore, when I used my version of ‘DefaultDesktopCommand ‘only one of my clients with Mac could not create a NoMachine session. Other Mac users and windows users are able to log in using my version of ‘DefaultDesktopCommand’ and get GPU acceleration. Kindly let me know your comments.
If you are still encountering the problem, please open a separate topic. This topic about virtual desktop on Linux can be considered solved.
Maybe you could go back to the developer of the project in question and ask them how to modify their script to use NoMachine instead of the other tool they are using? 😉
User was contacted via email.
Any feedback will be considered as we redesign the implementation of mouse support, taking advantage of the new APIs provided by the most recent iPad versions. We’ll also investigate the specific behaviour you have been encountering with the mouse model you
mention (middle button not working). Either way, in version 8 improvements will be made, so watch out for those.Thanks very much for taking the time to let us know. It’s certainly information that is useful for our developers.
We never received the log file, so what I suggest at this stage is you update to the latest version and if you are still seeing the same issue, submit the logs.
I just realised there is a ‘1’ missing in the key I wrote. I apologize for that.
The key should look like this:
DisplayServerExtraOptions “-displayrequired 1”Hi, thanks so much for your feedback 🙂
but in many other contexts, like the context we have, with machines both inside and outside the network.
This is exactly why we implemented it, to make adding nodes to your Cloud Server as seamless as possible.
you’ve changed the way you pick mouse position in Wayland, directly from udev which conflicts with other virtual input devices, blocking access to the remote desktop’s input, when the same is running an automation task…attempt to get mouse movements/control on the NoMachine client side.
What you describe is a new feature giving keyboard and input events from the local user logged-in to the remote computer priority over input generated by the user connected via NoMachine.
It is mainly intended to add a further security level to desktop sharing, so that the input (mouse and keyboard) of
the remote user connected by NoMachine will be effective only after the local user doesn’t produce any input for a certain period. When the NoMachine user gains control over keyboard and mouse, the local user can stop him/her at any moment by simply moving the mouse or typing something.To disable this behaviour, you can set this in node.cfg:
DisplayServerExtraOptions "-eventdelay 0"Your Android app is unparalleled when it comes to ease of access and keyboard functionality, and with Wayland support, you’ve been paramount to a whole section of the Linux comunity. We’re not going anywhere, we just want to use the old v7 server.
That’s good to know 🙂 You can try contacting the web team via the website to see if they can share a link to the earlier version. But first we would appreciate knowing if the -eventdelay setting improves things for you with regard to the mouse position issue you mentioned.
Regarding the SW/HW/white screen issues described in the thread, we are still investigating.