Forum Replies Created
-
Posts
-
Update: After playing around with xdmcp preparations, the mouse click problem resolved itself, although the NoMachine desktop I reach has a few remaining problems. For one, the Applications menu (and other menus) are browsable but do not acknowledge clicks…Except, oddly, for the Activities Overview. From the latter’s window I *can* launch Terminal and other apps (weird, eh?).
Anyway, xinput from within the NoMachine desktop yields different results:
Virtual core pointer id=2 [master pointer (3)]
Virtual core XTEST pointer id=4 [slave pointer (2)]
Avocent Dell 03R874 id=8 [slave pointer (2)]
Avocent Keyboard/Mouse Function id=10 [master pointer (2)]
Avocent Keyboard/Mouse Function id=11 [master pointer (2)]
Virtual core keyboard id=3 [master keyboard (2)]
Virtual core XTEST keyboard id=5 [slave keyboard (3)]
Power Button id=6 [slave keyboard (3)]
Avocent Dell 03R874 id=7 [slave keyboard (3)]
Avocent Keyboard/Mouse Function id=9 [slave keyboard (3)]
(In my previous post, the lines starting with ‘Virtual core keyboard id=3 [master pointer (2)]’ should read ‘master keyboard’ instead, sorry)
I have what may be a related problem. I installed NoMachine on a server (CentOS 7.5, nomachine_4.6.4_13_x86_64.rpm) and a client (Linaro on Parallella, nomachine_4.6.4_1_armhf.deb). I’ve previously been using NoMachine to control other Linux (Ubuntu) systems from Windows 7, with no trouble. But this particular setup has a serious mouse problem: the mouse moves, but cannot click! The keyboard seems okay (I have yet to make sure the keyboard config is correct, using mostly tab and space so far). If I ‘ssh -X’ into the server, here is what xinput says:
Virtual core pointer id=2 [master pointer (3)]
Virtual core XTEST pointer id=4 [slave pointer (2)]
Dell Dell USB Optical Mouse id=7 [slave pointer (2)]
Virtual core keyboard id=3 [master pointer (2)]
Virtual core XTEST keyboard id=5 [slave pointer (3)]
CHICONY USB Keyboard id=6 [slave pointer (3)]