Forum Replies Created
-
Posts
-
We’re not able to reproduce this. Did you perhaps change something in your settings. Are you able to share your server.cfg with us? You can send it to forum[at]nomachine[dot]com.
Hi, this pop up is to show the desktop owner that someone is connected to their desktop. It can be closed by clicking on the ‘x’ or by going into the NoMachine systray icon and disabling it from there. Please see for more details: https://kb.nomachine.com/DT07S00239#5.1. It’s especially useful for when another user is connecting to your desktop in Guest Desktop Sharing mode (https://www.nomachine.com/getting-started-with-guest-desktop-sharing).
That you can’t close is odd, so we need further details.
Are you connecting to a NoMachine Free Edition or one of the Terminal Server products?
Can you tell us the version of Ubuntu and what desktop environment it is?Hi, the setting is exactly the same, however, when applied to the connection it has effect only on that connection, on these ‘Connection settings’. Applied to the node it will have effect on all connections to that node.
Hi,
my laptop set to do nothing when the lid is closed if on power but if I close the lid
We cannot reproduce this. In our own tests the Windows laptop is set to “Do nothing” in the “When I close lid” configuration of both battery and plugged in options, the laptop is visible in the Player’s Machines panel and it’s possible to connect to the laptop. Can you show us a screenshot of your Windows settings?
What Windows version is it?
open the lid and restart the server
Do you mean that when you open the lid the OS restarts? Or when you open the lid you have to restart the NoMachine server (but the OS is still running)? Have you checked that the IP of that Windows computer can be pinged even with the lid closed?
I’m just using touch screen and keyboard on my Android device for mouse and keyboard input to the remote PC.
Thanks for the clarification.
We aren’t aware of issues with inputting from Android clients. Are you able to connect from another computer in place of your Android device and encounter the same problem? This would indicate it’s not an issue on the Android side.
You can use Xev to debug keyboard and mouse events on Linux. See this article for how to get the output.
https://kb.nomachine.com/AR12N00911. This will show if events are being received.Logs would be useful in any case. For server side logs: https://kb.nomachine.com/DT11R00182#1 (or enable log level in Server status -> Server logs 7- Verbose), then from a prompt run
sudo /etc/NX/server --debug --collect. Send everything to forum[at]nomachine[dot]com making sure to use the title of the topic as the subject of your email. Thank you.What kind of mouse and keyboard are you using with your Android client device? Is it bluetooth?
What about if you use just the screen of your device to input in to the remote desktop window? Do you still get the same behaviour?
Are you able to try a connection from a regular PC NoMachine client in place of your Android device?
What’s the desktop environment on your Manjaro Linux server?
What version of NoMachine is installed there? The latest 8.1.2?
Hi, we’re putting a special binary together and we’ll be in touch when it’s ready 😉 Thanks for everyone’s patience.
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