Open sredman opened 1 year ago
Are you able to compile and use the version of EVDI in the devel branch?
Like sredman I am suffering from the same problem. I will give it a try and give feedback.
Unfortunately, KWin is still unusable under Wayland if I disable KWIN_FORCE_SW_CURSOR=1 in /etc/environment.
Same issue for me, before I found out about setting the KWIN_FORCE_SW_CURSOR option, I got the exact same issue. I am using the lenovo thinkpad display link dock "Bus 004 Device 005: ID 17e9:433f DisplayLink ThinkPad USB 3.0 Pro Dock" If it helps here is dmesg output of me connecting the dock, then at line 250 I move my mouse and captures the errors, before I applied the fix. Since then it is working fine, but will test for you if a fix is patched.
Running plasma wayland and evdi-git 1.12.0.r6.gbdc258b-1 on Arch 6.1.1-arch1-1
Are you using the latest driver?
Are you using the latest EVDI version?
If you are using a DisplayLink device, have you checked 'troubleshooting' on DisplayLink's website?
Is this issue related to evdi/kernel?
Linux distribution and its version
Linux kernel version
Xorg version (if used)
Desktop environment in use
Since Kwin v5.25.1 (kwin commit f07d6bd40034372b7176f57de080003c8a612d57, to be precise), the evdi display appears to disconnect when the mouse is moved onto that screen. This commit in kwin started using gbm for the mouse cursor. If we set the environment variable for kwin to use software cursors, the issue does not happen.
The dmesg logs are attached to the KDE bug report. The KDE developer who developed most of the multi-GPU support in kwin feels this issue is in evdi. I can compile both evdi and kwin to help test.
KDE bug report is here: https://bugs.kde.org/show_bug.cgi?id=459929