- This topic has 1 reply, 2 voices, and was last updated 3 weeks ago by
.
-
Posts
-
Bug Report for NoMachine
System Information:
Operating System: macOS 12.7.6 (21H1320)
Kernel Version: Darwin 21.6.0
Boot Mode: Normal
Secure Virtual Memory: Enabled
System Integrity Protection: Enabled
NoMachine Version: 8.16.1 (8.16.1)Issue 1: Window Focus Problem on Initial Connection
Description:
When connecting to a remote server using NoMachine on macOS, the NoMachine window does not have focus initially. To interact with the remote session (e.g., typing or clicking), I must first click outside the NoMachine window and then click back inside the window to gain focus. This behavior occurs every time I establish a new connection.Steps to Reproduce:
Open NoMachine on macOS.
Connect to a remote server.
Attempt to type or interact with the remote session immediately after connection.
Observe that the window does not have focus.
Click outside the NoMachine window and then click back inside the window.
Observe that the window now has focus and interaction is possible.
Expected Behavior:
The NoMachine window should have focus immediately after connecting to the remote server, allowing the user to interact with the session without needing to click outside and back inside the window.Impact:
This issue is highly disruptive, especially for users who rely on NoMachine for daily tasks. It adds unnecessary steps to the workflow and reduces productivity.Issue 2: CAPS LOCK State Mismatch
Description:
There is a mismatch in the CAPS LOCK state between the local macOS client and the remote server. When CAPS LOCK is off on the local machine, NoMachine incorrectly indicates that it is on in the remote session. To resolve this, I must toggle CAPS LOCK multiple times (ON/OFF/ON) until the state is correctly synchronized. This issue occurs consistently on every connection.Steps to Reproduce:
Ensure CAPS LOCK is off on the local macOS machine.
Connect to a remote server using NoMachine.
Observe that the remote session indicates CAPS LOCK is on, even though it is off locally.
Toggle CAPS LOCK on the local machine (ON/OFF/ON) until the remote session correctly reflects the CAPS LOCK state.
Expected Behavior:
The CAPS LOCK state should be accurately synchronized between the local macOS client and the remote server immediately upon connection. No manual toggling should be required.Impact:
This issue is frustrating and time-consuming, especially for users who frequently type in all caps or rely on accurate key state synchronization. It disrupts the workflow and requires unnecessary manual intervention.Additional Notes:
Both issues occur consistently on macOS 12.7.6 with NoMachine version 8.16.1.
The window focus issue has been present for several versions of NoMachine, but the CAPS LOCK issue appears to be more recent.
These issues significantly impact the usability of NoMachine for daily tasks.
Request:
Could the NoMachine team please investigate and resolve these issues? They are causing significant frustration and inefficiency in our daily workflows. Any updates or fixes would be greatly appreciated.Thank you for your attention to this matter.
We are aware of the first issue and are currently investigating possible solutions.
With regards to the second issue, the default behaviour of NoMachine with regards to CAPSLOCK is that it does not interfere in any way with the physical status of CAPSLOCK of either machine. The remote side is synced to match the local client when you start typing.
This means that if your CAPSLOCK is ON on the local client, and you start the session, and on the remote server side CAPSLOCK is OFF, it does not automatically come ON on the remote side. However, if you start writing, you will get CAPS.
Similarly if you have it OFF on the local side, and CAPSLOCK is ON on the remote side. It stays ON on the remote side. However, when you start typing, remote status is synced to match the client status and there will be no CAPS.
Is what I have described does not match what you are experiencing in your set-up?
You must be logged in to reply to this topic. Please login here.