https://bugs.winehq.org/show_bug.cgi?id=51420
--- Comment #22 from matt gardotd426@gmail.com --- (In reply to Kurt Kartaltepe from comment #19)
I can't reproduce this at all on 495.44 (and I've never seen it before on any driver version since I got the 3090 on launch day on 24 Sept. 2020), so I'm guessing this is probably limited to older drivers/cards now.
It is trivially replicable on 6.21 by running regedit.exe and trying to use it. I am using a GTX 1070. I wouldn't classify this as "older drivers/cards" as basically all newer models are unattainable by the average user. As my wallet and time is not unlimited I dont have other hardware to test personally.
I have regedit open right now and Nvidia is at 2.23% with sudo perf top -p $(pgrep Xorg). I'm even compiling the kernel and it's not slowed down at all, and gotop doesn't show Xorg in the top 20 cpu processes.
Obviously this is still an issue for some people (that is weird though, that it's only some people that have the issue), but it would be nice if we could figure out why some people say it's fixed, some people say it's not, and others could never reproduce it in the first place.
I am able to reproduce this bug on 495.44-13 driver published in the official >arch repos on November 26th on an RTX 2060 super card. I'm willing to bet this >is a multi monitor issue.
There is another big teport that also mentions an external monitor and is almost >certainly a duplicate of this bug:
I have 2 monitors and have for the entire time I've had an Nvidia GPU (over a year), and haven't seen this issue once.
That doesn't mean it's not in some way related to monitor setup, but it's not "if you have an Nvidia GPU and multiple monitors you have this bug."
I was hoping I could reproduce it so I could maybe try and test some stuff to help debug it, but I can't do much if I've never had the issue and can't force it.