- This topic has 13 replies, 6 voices, and was last updated 8 years ago by
.
-
Posts
-
I upgraded both my client and server machines to El Capitan and NoMachine on both to v5.1.7. When I connected to the server, things looked fine, but when I click buttons on my mouse nothing happens. I saw that there was an even newer version, so I upgraded to v5.1.9, but I’m still seeing the same problem. The mouse pointer moves around (you can see visual differences as it hovers over things), but I can’t click on anything. Any settings I can change to fix this?
Hello
I think this issue was reported already: https://www.nomachine.com/TR03N06573.
Please check ‘notify me’ to know when it has been fixed.
I can confirm this behaviour on MacBook Pro with OSX El Capitan server running NoMachine 5.1.9 – the behaviour was exhibited in the previous version of NoMachine as well. Keyboard events (keypresses) are registered and acted on as expected but with mouse activity, *only* movement events are registered and acted on accordingly. Mouse button clicks do not register at all.
Both “Grab keyboard input” and “Grab mouse input” are not selected in the client that is accessing the OSX El Capitan NoMachine server but enabling them does not change anything either (in terms of getting the NM server to register mouse button clicks).
I’m using the Linux NoMachine client (to connect to the El Capitan NoMachine server v5.1.9). Connecting to a Linux NoMachine server (also v5.1.9) does not exhibit this behaviour – both keyboard and mouse events [cursor movement and button clicks] are registered and acted on accordingly.
This behaviour is not a duplicate of https://www.nomachine.com/TR03N06573 although I can confirm the that the symptoms described by this ticket do also occur as described there.
Thanks! It turns out that I am affected by that problem (just had to restart the server in order to unlock it), but although they may be related, the one I was reporting is a bit different. Mouse clicks on the client aren’t registering as mouse clicks on the server while remotely connected. As I said, given that there are issues associated with mouse and keyboard control, they may very well be related.
I am also affected. Is there some workaround? Alternatively, is there some way to roll back to a previous version without this bug?
Thanks. I meant to mention here that I was given a debug copy of v5.1.9 in order to help diagnose the problem mentioned in https://www.nomachine.com/forums/topic/nxnodebin-cpu-usage-jumps-with-5-0-58 and that appeared to fix the problem described in this thread.
By the way, on a separate note, I always check the “Notify me of follow-up replies via email” box below but I never get follow-up emails. That’s the main reason I didn’t reply here until now.
@graywolf – if your post wasn’t an April Fool’s joke, I’ll test your possible solution.
@mpassel – When did you get the debug copy of v5.1.9 for Mac?
@animaniak – I got the debug copy of v5.1.9 on March 10th.
I am experiencing the same issue. From /var/log/system.log, I see this:
===
Apr 8 22:08:53 darpohsh-wsm WindowServer[217]: Warning: Program “nxnode.bin” posted a mouse-down, blocking hardware events, but did no further mouse activity
Apr 8 22:09:24 — last message repeated 24 times —
Apr 8 22:13:27 darpohsh-wsm WindowServer[217]: Warning: Program “nxnode.bin” posted a mouse-down, blocking hardware events, but did no further mouse activity
Apr 8 22:13:28 darpohsh-wsm WindowServer[217]: Warning: Program “nxnode.bin” posted a mouse-down, blocking hardware events, but did no further mouse activity
Apr 8 22:13:53 — last message repeated 10 times —
===
I’m having the same problem, with the same thing showing up in system.log. I hope it gets fixed soon, as it makes nx completely unusable for me.
This topic was marked as solved, you can't post.