October 13, 2017 at 07:37 #16043
Remote: NoMachine – Version 5.3.12 (free version?) running on CentOS release 6.9 (Final)
Client: current, used from Win7, CentOs, Fedora machines, various desktops – with same behavior.
Connecting to the physical display:0
remote machine desktop: tried XFCE4 (works best) / gnome (sluggish)/ kde (sluggish) all show same behavior
Hi, frequently I’m running into this mouse related issue when logging in remotely through nx.
The mouse is either partially or totally inoperable. The curser can be seen moving as expected, but clicks are no-op, either totally, or for certain X operations like raise, lower, focus, or when trying to attempt using any session menues.
Sometimes the buttons seem to be switched, right click does something that should be left click, sometimes right click seems like both.
No visible error messages.
It always starts at the begin of a session, and there seems no way to change the behavior while being remote. (except rebooting the server – that clears it.)
It persists despite repeatedly connecting / disconnecting the client, or across various clients.
Using the server console directly resets the problem immediately. Sometimes it seems like all the attempted operations are cycled trough very quickly at the begin of the console session. Console is on screenlock while connecting remotely.
Anybody has seen this too?
(been using NoMachine before on a remote Centos 5 machine for a long time, no mouse problem with that)
Any input would be welcome.
thanks,-wolfgangOctober 16, 2017 at 12:00 #16077graywolfParticipant
did you try to run xev tool in the remote session when the problem occurred? that sounds like any modifier key stayed in the “pressed” state.October 17, 2017 at 08:15 #16084
didn’t now about that tool. I will run it next time the issue shows up.
Thank you!!October 20, 2017 at 08:19 #16133
today it happened again. Logged into the host through NoMachine, and the mouse had no effect. One shell window happened to be “on” so i started xev in there. Its little box window appeared, and I tried to click it, with no visible effect.
During all of this that shell lost focus, And I couldn’t get that back remotely.
Asked someone in the office to turn on the host terminal and click onto something, that unlocked the situation completely, also on the client.
So the log of that experiment is attached. I hope it contains some useful information to resolve this crazy situation.
Let me know…
Thank you!!!October 20, 2017 at 08:20 #16140
Please forward the mouselog to forum[at]nomachine[dot]com. Thanks!October 23, 2017 at 09:13 #16150
Hi there. I having issues with mouse with Windows 10 too. How to supply the mouse log?October 25, 2017 at 09:34 #16176graywolfParticipant
@w_ri: in the xev output the mouse events are completely missing. We need to rebuild NoMachine libs with verbose logging enabled in order to find where events are lost. We’ll contact you by mail to provide the debug libs.
@graphixillusion: Windows is the server, I guess. In that case xev is useless for debugging. Please write to forum[at]nomachine[dot]com to receive debug libraries and instructions.October 26, 2017 at 08:09 #16193
The remote machine is RH6 (Centos6.1). Thats where i started xev. The client is Win7. Yes, when it happens the mouse has no effect on the remote machine. Going onto the remote terminal, and using the mouse there unlocks the situation. Sometimes it appears the mouse curser is wiggling around like doing all the clicks that were attempted remotely within a fraction of a second. But it may be an illusion.
Thanks for looking into this.October 30, 2017 at 16:12 #16227
Mail sent but still didn’t receive anything. This mouse issue is very frustrating!October 30, 2017 at 16:17 #16231October 31, 2017 at 08:25 #16237
ok thank you.November 28, 2017 at 15:26 #16738
@graphixillusion, we need to send you another attachment to try, but emails to you come back to us undelivered.
further analysis showed that mouse clicks look OK. The cause could be a Ctrl or Shift key stuck in the “down” state. Running the attached test tool from command line will help to inspect the state of keys on mouse clicks. Run:
wintest.exe > wintest.txt
do some left clicks, close the wintest window and let us look at
Can you get in touch?
Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.