Second monitor display not responding to mouse clicks

[noetus]

I have an issue with a dual monitor setup on Windows 8.1 (not high DPI) where NoMachine does not respond to mouse clicks on monitor B.  That is the monitor I want to use, so this is a problem.   It does respond to hover events, but not to click events.

I have to switch NoMachine to Monitor A to log in (by going out of fullscreen display and using a separate display management application to push the window to the other monitor) and then go back and forth between the monitors a few times, experimenting with entering and
exiting full-screen, and after a bit of this it starts responding to mouse clicks again on monitor B.

I see this has been a problem before:

https://www.nomachine.com/forums/topic/nomachine-monitor-doesnt-respond-to-mouse-clicks

The most recent update of NoMachine did not resolve the issue.

[fra81]

Hi noetus,

unfortunately the problem is not clear to me. Can you please let us know:

1) Windows 8.1 is on client or server side? What platform is on the other side?

2) Dual monitor is on client or server side (or both)?

3) Is it the NoMachine player GUI that doesn’t receive clicks or the remote desktop?

4) When you say that you can’t log in, you mean that you can’t log in from the client to the remote session, or that the remote system is in the login screen and you can’t log in to the desktop?

5) What is the display manager application you are talking about?

[noetus]

Windows 8.1 is the client.  The server is Mac OS, but actually this is irrelevant.  I encounter the problem just starting NoMachine, without any server connected, and without it having found any servers on my network. So it is clearly a problem with the GUI.  I can’t log in or do anything, even minimise the GUI, because it isn’t responding to mouse clicks.

I have two monitors on the Windows 8.1 client, my main monitor and my secondary monitor.  When starting NoMachine on the secondary monitor (the one I use most often because it is much larger) it the GUI does not respond to mouse clicks, though it does respond to mouseovers.  To get it to start responding to mouse clicks, I can either close it (I have to use Task Manager for this and kill the process, as it is not responding to mouse clicks to close) and open it again on the primary monitor, or I can move the app over the primary monitor using something like DisplayFusion or Active Window Manager or something like that.

[noetus]

No replies yet for this issue?

My workaround is to start NoMachine on the primary monitor, connect to server, set fullscreen to off, set display resize to off, move NoMachine to secondary monitor, set fullscreen to on, set display resize to on, and log in.  However, though this usually works, it isn’t guaranteed to.

[Tor]

Hi noetus.
We’re testing different configurations to reproduce your issue, so far with no success.

My workaround is to start NoMachine on the primary monitor, connect to server, set fullscreen to off, set display resize to off, move NoMachine to secondary monitor, set fullscreen to on, set display resize to on, and log in. However, though this usually works, it isn’t guaranteed to.

Does the same problem occur if you keep fullscreen and display resize disabled?
Could you send a screenshot of your ‘Screen Resolution’ dialog to see how your monitors are arranged?

[Author]

Posts