https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #52 from Jeffery Patton <roundduckm...@gmail.com> --- (In reply to Guilherme Almeida from comment #49) > (In reply to Erik Kurzinger from comment #48) > > (In reply to Guilherme Almeida from comment #47) > > > (In reply to Luca Carlon from comment #22) > > > > Hello, I'm also affected by this issue. It is so severe that the system > > > > was > > > > hardly usable. I just noticed one thing: I suspect the issue appears > > > > for me > > > > only when drm is enabled with nvidia-drm.modeset=1. By default this was > > > > not > > > > set in Kubuntu 18.10 and 19.04 (may explain why Peter Eszlari could not > > > > reproduce?). Unfortunately drm is the only way I found to prevent > > > > horizontal > > > > tearing. > > > > No idea if this info is already known or of any help to you. > > > > > > I can confirm that, Luca. Using PRIME on Manjaro 18.0.4, I changed > > > /etc/modprobe.d/nvidia-drm.conf, setting like this options nvidia_drm > > > modeset=0 and the the frezze has stoped. I haven't noticed tearing so far, > > > but if happens I will edit this reply. > > > > Note that the reason this resolves the issue is that is disables PRIME > > synchronization entirely (see > > https://devtalk.nvidia.com/default/topic/957814/linux/prime-and-prime- > > synchronization/ for details). So tearing would be expected, since this is > > how the NVIDIA driver is made aware of each vblank by the Intel driver. > > > > Only disabling vsync for the QtQuick pop-ups would definitely be a > > preferable solution, I think. > > Yeah, I've noticed... Is strange that this problem affects users from > differents ways? I mean... One user reported > (https://forum.manjaro.org/t/kde-plasma-freeze-when-i-use-screen-edges-kwin- > hang-regression/88897/31?u=fvguilherme) that simple install kwin-lowlatency > from AUR instead of kwin has solved the problem. > > and yes, I've noticed a little horizontal tearing. I choose keep the freeze. The reason that fork doesn't seem to suffer a problem is that it's focused on a whole bunch of fixes for rendering as a whole, like the bugs that makes KWin hard to run at 144Hz, and either these fixes also counteract the freezing regression to Nvidia Optimus, or it never had the code added to it in the first place, since it's a fork that predated 5.14.4. -- You are receiving this mail because: You are watching all bug changes.
