Forum Replies Created
-
AuthorPosts
-
Britgirl
KeymasterHi, can you enable grab the keyboard in the connection menu (connect first, open the menu with ctrl-alt-0), proceed to Input)?
More details here: https://kb.nomachine.com/DT06S00218#3
Keyboard
Grab the keyboard input – Ticking the box disables the capturing of some system key combinations allows you to use those shortcuts in the remote desktop.Britgirl
KeymasterPlease show us the list of processes showing such high CPU usage. Also, logs from the ECS server host, also knowing what OS version it is would be useful as well.
Britgirl
KeymasterHi, I removed your public IP from the log excerpt for privacy reasons. Is there a specific reason for using version 8.9 to connect? Have you considered updating it? This would narrow down the issue so that we aren’t investigating older versions to find out that the problem was being caused by something already fixed.
That said, we would need the server-side logs so we can check them. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. It’s important to enable debug, reproduce the error, then zip up the logs.
Also the player logs would be useful as well. (instructions are in the same document)
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Britgirl
KeymasterHi,would you able to send us the server-side logs so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. It’s important to enable debug, reproduce the error, then zip up the logs.
Also the player logs would be useful as well. (instructions are in the same document)
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
March 7, 2025 at 18:57 in reply to: No Windows screen lock when NoMachine client on foreground #52161Britgirl
KeymasterApologies, I didn’t point out that this is a global setting, and requires you to exit the Player first (Quit the player from the system tray !M icon), make the requested change and save, then re-open the Player. Can you try again?
We’re investigating it our side as well in the meantime.
Britgirl
KeymasterHi, no there isn’t. This is to keep the number of shortcuts to the minimum to avoid clashing with system shortcuts.
The shortcut options available (and which you can edit if you prefer) can be found in the Player settings > Input > Shortcuts.Britgirl
KeymasterHi, this is a valid request for connections to the physical desktop and should be relatively easy to do, so we’ll open a feature request. Are you also handling users connecting with guest desktop sharing? Because if that’s the case, the name of the desktop owner cannot be shown for privacy reasons and so this FR will not apply to that type of user.
March 7, 2025 at 17:33 in reply to: No Windows screen lock when NoMachine client on foreground #52152Britgirl
KeymasterIs the session in fullscreen when you encounter this? When the session runs in fullscreen mode, NoMachine disables the display sleep timer in order to offer users a more comfortable experience (such as when streaming media). There’s a key that should regulate this. In .nx/config/player.cfg, can you edit the key “Turn off energy saving while in fullscreen mode” to false? Does this help?
Britgirl
KeymasterPlease execute the following on the Linux side and send us the output.
ps -aux | grep nxnode
Then read the
PID
And then:
cat /proc/<PID>/environ
Britgirl
KeymasterSo the computers are on the same LAN, and they can see each other.
By default, when you are prompted to input the credentials of the system account of the desktop you want to connect to, if you don’t use the same credentials as the owner of that desktop, you will need authorization of the owner. Check the NoMachine security settings on the Zorin host (Server settings > security > that the following option is enabled:
Don’t require acceptance if the user logged in as the owner of the desktop
Enabled by default. If someone is trying to connect to your desktop, a pop up message asking for your permission appears. By default such authorization is not requested if the connecting user is also the desktop owner, or if he/she is a system administrator or a NoMachine administrator or trusted user.https://kb.nomachine.com/DT07S00237#2.5
If that option is enabled, and the balloon notification is popping up when you connect, it means you are not the owner of the desktop.
About the connection timeout issue when connecting to the Windows host, go into ‘Edit connection’ in Machines and check what is in the host field. Are there multiple IP addresses? See here for a similar topic I answered a while back: https://forum.nomachine.com/topic/how-to-make-nomachine-update-target-computer-ips#post-39467
March 6, 2025 at 19:34 in reply to: NoMachine window not responding or glitching on Mac Sonoma #52144Britgirl
KeymasterThere are some things which are not clear:
What is the OS you are connecting from (client side)?
What is the OS you are connecting to (server side)? If the server is on macOS, confirm that NoMachine has accessibility permissions.
What is the NoMachine version you are using, client and server?When you write “before I can access a window that responds to my mouse” do you mean you can’t interact with the server desktop through the NoMachine window?
Britgirl
KeymasterHi, I’ve split this off to start a new topic because you submitted it to a topic which was about macOS, so best to keep them separate.
Britgirl
KeymasterIt’s a bug on the server side, but this problem will be removed when v9 comes out. The default timeout will be 30 secs in version 9.
Britgirl
KeymasterYes, it seems there are a few issues with the latest Ubuntu and RPi5 (not NoMachine issues). You might also consider using XFCE instead of Gnome.
Britgirl
KeymasterAn update: we have to backtrack on what we last wrote. We thought we had reproduced the same issue, but it was a false allarm. It seems to be related strictly to Android Studio. We will keep investigating and update here if we find anything. I imagine you’ve already tried:
– adb kill-server
-revoke usb debugging authorisation
-
AuthorPosts