Forum / NoMachine for Linux / Intermittent loss of keyboard/mouse
- This topic has 6 replies, 2 voices, and was last updated 5 years, 8 months ago by  graywolf. graywolf.
- 
		AuthorPosts
- 
		
			
				
February 4, 2020 at 08:34 #25465 EddieAParticipant EddieAParticipantRunning version 6.9.2 on a Slackware 14.2 system. Connecting from Windows 10, Enterprise Clint 6.9.2. Very intermittently I will lose the ability to enter anything via the keyboard or mouse clicks. The client is still seeing the mouse, because if I hover over menus, status bar, etc. I still get the pop-ups, so it’s registering the mouse position. I just can’t click on anything or use the keyboard. Not sure what information you would want when this happens. Cheers. February 4, 2020 at 12:06 #25473 graywolfParticipant graywolfParticipantHello, likely a modifier got stuck in “key down” state. Should such issue occur again, press/release all Alt/Shift/Ctrl keys and let us know. February 4, 2020 at 17:23 #25479 EddieAParticipant EddieAParticipantOK, will do. Although I wouldn’t have thought that would have caused all keyboard and mouse actions to be blocked. I would have unexpected “strange” results. Cheers. February 5, 2020 at 09:32 #25482 EddieAParticipant EddieAParticipantActually I hadn’t killed anything yesterday, when I reported this, so connecting again, it’s still in the same “no input” state. Tried mashing every single key on the keyboard multiple times. No effect. Cheers. February 10, 2020 at 18:29 #25564 graywolfParticipant graywolfParticipantIs it your server user session on Wayland or Xorg? If it is Xorg, you could check if any mouse/keyboard grab is active when such loss of keyboard/mouse occurs. February 11, 2020 at 09:13 #25565 EddieAParticipant EddieAParticipantMy environment is described here https://forums.nomachine.com/topic/still-cannot-find-default-environment-after-tr09n07188-fix Cheers. February 11, 2020 at 16:47 #25601 graywolfParticipant graywolfParticipantSo you have one virtual NoMachine display. You can check input with xev: - Connect by NoMachine to the troublesome session.
- Connect by ssh to the NoMachine server and run this command to find the display number of the session and exporting to terminal: export $(cat /proc/$(pgrep nxclient.bin)/environ | grep -z DISPLAY)(there is only one session, so only one nxclient.bin)
- Run the xev command in the ssh terminal. The xev white window will show up in the NoMachine session. Try to hover, click, type in the window. Check the results in the ssh terminal.
 Then, you can list the apps grabbing the mouse/keyboard: - Run the command  xdotool key XF86LogGrabInfoin the ssh terminal.
- Check the result in session log file. Find it with command  /usr/NX/var/log/node/C-*$(cat /proc/$(pgrep nxclient.bin)/environ | grep -z NX_SESSIONID | cut -f2 -d= )/session
- You can terminate the grabs with command: xdotool key XF86ClearGrabor kill the grabbing app.
 
- 
		AuthorPosts
This topic was marked as solved, you can't post.

