New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DisplayLink Club3D CSV-1477 video adapter: mouse can go off-screen when using multiple monitors #20
Comments
Email reply from: technical-enquiries@synaptics.com
|
My tasks:
|
Ubuntu 22.04 results on Dell Precision 5570 high-end 20-core laptopOk, when I just plugged in those two monitors again, I did not get the mouse-going-offscreen behavior. So, I plugged in a 3rd monitor, and now I do. Here's my configuration: Yellow shows where I can move my mouse off-screen, but should not be able to: Monitors:
The Club3D DP to USB-A adapter is plugged into a USB 3.0 type A hub which is connected to the laptop via a USB-C port. Log file generation command: |
Ubuntu 20.04 results on weaker 8-core Dell Latitude 7490 laptopSame: when I just plugged in those two monitors again, I did not get the mouse-going-offscreen behavior as before. So, I plugged in a 3rd monitor, and now I do. Here's my configuration: Yellow in the Ubuntu 22.04 comment above shows where I can move my mouse off-screen, but should not be able to. Monitors:
The Club3D DP to USB-A adapter is plugged straight into a USB 3.0 type A port in the laptop. Log file generation command: Driver installation instructionsNote: here is how I installed the driver on this computer: Full instructions: installing displaylink-driver on Ubuntu 20.04 (also applies to 22.04 or later). |
My latest email to Kate:
|
Another setup with the problem: Ubuntu 22.04 with 2 monitors (only 1 in the Club3D adapter)
Monitors:
Mouse can go off-screen in this yellow region:
My email describing this:
|
To clarify for the setup just above: when I remove the Club3D adapter entirely, and direct-connect the 4k monitor via a DP to USB-C adapter, and direct-connect the 2k monitor via a USB-C cable straight from the monitor, I do not get the above aberrant behavior where the mouse can go off-screen. I can also direct connect the 2k monitor via an HDMI cable to an HDMI to USB-C adapter, and again, I do not get the aberrant behavior. I only Get it when using the Club3D adapter. Here is the setup that does not have the problem:
Here is the other setup that does not have the aberrant behavior:
The mouse-going-offscreen aberrant behavior is only present when using the Club3D adapter, and even then, only in certain configurations as described above. |
Upstream xserver bug report that the DisplayLink Technical Support team opened up and emailed me about: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1600 |
Quick summary
I can move my mouse off-screen into the sections in yellow here. I shouldn't be able to move my mouse past the edge of any monitor, so this is a definite bug. When not using this adapter at all, but using the same computer, monitors, and setup, I do not see this bug, and my cursor is properly blocked from exiting the edge of all monitors.
Details
sudo apt install displaylink-driver
)I installed the DisplayLink driver per my instructions here: https://askubuntu.com/a/1486986/327339:
In certain multi-monitor configurations, however, I can move the mouse off of the monitors into the dead corner spaces between monitors. I should be blocked from moving the mouse off-screen, but again, the bug is that I am not blocked from doing so. The problem only seems to exist when driving really high-resolution monitors (ex: 4k 32"), while other monitors are plugged into my computer too, even by other means.
Here is the most basic monitor setup exhibiting this bug (I removed a monitor for the purposes of this demo):
When in this configuration, I can move the mouse off the screen to all the corners shown in yellow. Again, this is the bug. I should not be allowed to move the mouse into these areas!:
When using a single external monitor in addition to my laptop screen, this bug does not seem to occur.
The text was updated successfully, but these errors were encountered: