Incorrect mouse interaction

Forums / NoMachine for Linux / Incorrect mouse interaction

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #7454
    Avatarvmajor
    Participant

    Ubuntu 14.04 x64 connecting to Lubuntu 15.04 i386 both using NX 4.6.4

    Mouse position and click status are wrong making the use of GUI impossible.

    I enabled the “show remote pointer” option to better understand what the remote GUI sees, and the remote pointer is offset by about 20% of the screen, and it jumps around as I drag the mouse on the local machine. The clicks are in rapid fire mode, ie. for every real click the remote machine receives several. Finally the remote cursor tends to jump or hover above the top right corner resulting in maximized applications being closed on every click presumably elsewhere on the local machine’s screen.

    V.

    #7505
    Avatargraywolf
    Moderator

    Hello.

    Could you send the output of command “xinput” that you get on the display of the server (Lubuntu 15.04) you are trying to share?

     

    #7653
    AvatarUrhixidur
    Participant

    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)]

    #7658
    AvatarUrhixidur
    Participant

    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)

    #7664
    AvatarUrhixidur
    Participant

    Curiouser and curiouser. After a reboot, the desktop now works fully and fine.

    #7671
    Avatargraywolf
    Moderator

    Urhixidur, my guess is that an inter-process communication issue existed among components of the desktop environment, so menu got the clicks but no action was performed.

Viewing 6 posts - 1 through 6 (of 6 total)

This topic was marked as solved, you can't post.