- This topic has 9 replies, 3 voices, and was last updated 11 months ago by
.
-
Posts
-
If an application is opened on the remote client and then the remote is closed, the scroll on mouse doesn’t work on the application when using the local machine running the server.
Closing the application and reopening it enables the scroll again.
Hi, you submitted to Linux and I assume you are connecting to Linux, but can you confirm the following please:
– NoMachine version on player and server sides
– Linux distro and version
– Desktop environment on Linux
– what application are you using?Does this happen in all applications?
NoMachine on server and client: 8.8.1
lubuntu 23.04
lxqt 1.2.0
It doesn’t scroll in LibreOffice and QTerminal but it works in Firefox and Thunderbird.
I upgraded to 8.9.1 on both ends (server and client) and the problem still happens.
If I open an libeoffice calc or qterminal through NoMachine and then close the connection, the app on the bare metal doesn’t scroll with the mouse scroll wheel.
Thunderbird scrolls.
Please run the ‘xev’ utility on the server and show us its output when scrolling. You should see a few ButtonPress/ButtonRelease events (of button 4 and 5), and these are the ones we’re interested in. Do this on the server before the connection (when scrolling works in all the apps) and then again after the connection (when you experience the problem).
There doesn’t appear to be any X events when scrolling.
On the server before connecting remotely (see attached)
qterminal doesn’t scroll on server after remote connection (qterminal left open during remote connection): (see attached)
I see that there are no X events reported by xev even before the connection. You have to keep the cursor on the xev window to make them appear. Can you try again in that way? No need to send the whole xev output, it would be enough to show just the scroll events, before and after the connection.
Sorry for the delay. I checked the logs and I see there is no difference in the scroll events before and after the connection, so we can exclude that NoMachine leaves the input events system in an inconsistent state. Even the modifiers state is exactly the same. I don’t know why those two applications stop handling scroll events, but it doesn’t seem anything that the NoMachine does wrong. One last thing you could try is comparing the outputs of the ‘xev -q’ command before and after the connection, in order to see if any of the X server settings has changed in the meanwhile.
This topic was marked as solved, you can't post.