Can connect, see desktop, mouse and keyboard don’t work

[martixy]

It used to work last time I used it, maybe a month or two ago.

Now I can no longer control the remote machine.

I connect from a Windows 10 machine to a Linux Mint 21.3.

I was on v8.something, and just updated both sides to v9.1.24, hoping that would resolve the problem. It did not.

No visible changes have been made on either side, apart from keeping both machines updated (e.g. windows update and apt update/upgrade).

I restarted both machines a couple of times as part of the latest round of updates (NoMachine demanded it on Windows and on Linux to free up the old kernel for delete).

 

I can connect to the machine btw, and see the desktop, and the cursor changes when I hover over the window, but no inputs are registered.

[katpan]

Hello,

Are you able to send us the logs from the server machine? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email.

Thanks!

[martixy]

Since I posted this thread I did some digging on my own.

I’d had trouble with NoMachine previously, as described in this thread: https://forum.nomachine.com/topic/mint21-no-mouse-wheel-scroll-in-some-applications.

It’s the same machine. The setting suggested in that thread now causes my new issue. Removing this setting fixes server not registering input; however, it restores the original problem of the linked thread.

Technically, the original problem is much lower in severity than not receiving any inputs, however ideally I would like to solve both.

Attachments:

1. NoMachine-log-1.zip

[martixy]

Btw, my eyes somehow glossed over the “send to email” part. Should I still do that?

[bucu]

Hi,
we’ve reproduced your problem and we’re working on a fix.

In the meanwhile can you try using Wayland instead of X11? You can do this by logging out and selecting “Wayland Experimental” from the icon next to your username. If yes, please remove -alteventapi key from node.cfg before starting such session. It should work as you expect.

[martixy]

Default (I assume X11): “-alteventapi 1” -> No input. No “-alteventapi” -> Input is back, problem from linked thread is back.

Wayland experimental: No “-alteventapi” -> No input. “-alteventapi 1” -> Have not tested.

After switching to Wayland, my DE bugged out, the UI of programs was missing and I could no longer lock screen/log out/shut down.

It required a couple of reboots to fix things.

[Britgirl]

Hi, we have a patch which fixes the problem, let us know if you’d like to try it. We can send you a download link to a free edition package. The patch is scheduled for release in the next update.

[martixy]

Which problem exactly does it fix?

Input failing when “-alteventapi 1”?
Or the scrolling issue from the other thread when “-alteventapi 0”?

In any case, it’s not critical for me. I can wait for the public release. (However if you would like me to verify the fix works, I am willing to do so.)

[Britgirl]

Which problem exactly does it fix?

This: “-alteventapi 1” -> No input.

[Bilbotine]

Hi martixy,

We are sending you a patch, please check your mailbox.

[er1c4rd]

Can I also get a patch? I’m facing the same issue-nothing works until one of my Sys Admins logs me in through HyperV. After that, I see a duplicate cursor following the main one.

[Author]

Posts