Bug 466200 - Region artifacts that follow mouse ghosting when all windows set to semi-transparent on Wayland with multi-monitor setup
Summary: Region artifacts that follow mouse ghosting when all windows set to semi-tran...
Status: REPORTED
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 5.27.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-21 16:21 UTC by Pasha
Modified: 2023-02-22 07:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Pasha 2023-02-21 16:21:57 UTC 
STEPS TO REPRODUCE
1. Have multiple monitors
2. Start KDE Wayland session
3. Set window transparency (through window rules)

OBSERVED RESULT
1. Cursor trail on desktop.
2. Main display (bottom-right). Bottom right portion of the screen is black, mouse movement in the top-left corners "wipes" black window away, similar to mouse trail.*
3.  Additional display (top). Right border of the screen is black, mouse movement in the left border "wipes" black window away, similar to mouse trail.*
* Happens both on desktop and all applications.

EXPECTED RESULT
No artifact regions and no mouse trail

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux (6.1.12)
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Nvidia proprietary driver, different refresh rates on all screens (120, 75, 60).
Turning blur off, turning any of the screens doesn't fix the issue.
Leaving only 1 display fixes the issue.
Monitor setup: https://postimg.cc/ZWkBxZXf
Bug showcase: https://youtu.be/tIT0kHvEeWY
Comment 1 Nate Graham 2023-02-21 22:37:24 UTC 
Bug 455526?
Comment 2 Pasha 2023-02-22 07:40:45 UTC 
(In reply to Nate Graham from comment #1)
> Bug 455526?

Mouse behavior is the same as in the bug, that you've provided. And it was the same for me prior to 5.27 update. 5.27 brought the bug that you can see in the youtube video in the bottom of my bug report (should I move it to the attachments?) and it is not displayed in the 455526 report.