Problems with mouse input: Centos8, TVNC+VGL, XFCE4.

[qwofford]

I noticed that in XFCE sessions, the mouse cursor is not present in my TurboVNC client view. The TurboVNC server produces the following log output:

06/10/2020 10:19:24 Client supports GII version 1

06/10/2020 10:19:24 GII Device Create: Stylus

06/10/2020 10:19:24 GII device ID = 1

06/10/2020 10:19:24 GII Device Create: Eraser

06/10/2020 10:19:24 GII device ID = 2

Which leads me to believe the mouse is not being identified correctly. I am connecting from a TurboVNC 2.2.5 client on OSX, with a Logitech G500 mouse (details of the mouse are attached). I noticed my xorg.conf has references to a mouse, so I posted this in the VirtualGL group originally, but I was informed that this config section is not relevant to IO in a combined TurboVNC/VirtualGL solution. The server is running on Centos8, with TVNC v2.2.5. The session desktop is configured to use XFCE4.

Note: I am also getting an "XFCE PolicyKit Agent" error when the TVNC desktop connects. I suspect this is a different problem, but mention here for the sake of completeness.

[DRC]

I sincerely apologize for the delay in responding to this.  This year has been really nuts, and it's only been within the past week that I have finally been able to pop the stack on TurboVNC issues.

Wacom tablet support is implemented in different ways on different client platforms.  For Linux/Un*x clients, we use the GII RFB extension to forward all relevant X Input devices in kind from the client to the server (that's what the GII extension was designed to do.)  For Mac clients, however, there is no analogue to X Input.  Tablet support is integrated into the O/S, and the TurboVNC Viewer doesn't know whether a particular tablet device is available until it receives a "proximity" event that tells it that the tablet device has entered the proximity of the viewer window.  Thus, the Mac TurboVNC Viewer mocks up two GII devices for the Wacom stylus and eraser and always creates those devices on the server via GII, regardless of whether a tablet is actually present or in use on the client.  The presence of those devices in the TurboVNC session is normal, but obviously the behavior you're observing isn't.

Please try running the viewer from the Terminal using

  /opt/TurboVNC/bin/vncviewer -loglevel 150

That will print any GII (ExtInputDevice) messages to the console.  You should see some initial output from creating both the stylus and eraser devices, but you should not see any additional ExtInputDevice messages as you move or click the mouse.  If you do see those messages, then that probably means that your mouse is being incorrectly detected as a tablet, which is a bug.

I also just pushed a commit that allows GII to manually be disabled by setting JAVA_TOOL_OPTIONS="-Dturbovnc.gii=0" in the environment.  The latest pre-release builds (https://turbovnc.org/DeveloperInfo/PreReleases) should have that fix.  Disabling GII will at least tell you whether that's the cause of the issue.  If it's not, then I have no other ideas.

--
You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to turbovnc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/bab3167b-15de-4603-9ed3-6c1f117a85b0n%40googlegroups.com.

[DRC]

The OP informed me that this issue was apparently due to missing Xfce packages.  It was not related to TurboVNC.