https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #32 from Jeffery Patton <roundduckm...@gmail.com> --- (In reply to David Edmundson from comment #28) > From Erik: > > "Alright, I think I see what the issue is. For context, on PRIME systems, > since there isn't actually a display connected to the NVIDIA GPU, we rely on > xf86-video-modeset, which drives the Intel GPU, to call to our driver after > each vblank. However, it will actually only do so if there has been damage > to the screen. So what I think we have here is QtQuick's thread waiting on > this vblank signal before swapping buffers (since we set MaxFramesAllowed to > 1), and KWin's main compositing thread waiting on the QtQuick thread. Since > KWin isn't rendering to the screen while it waits, no damage occurs and > hence this vblank signal is never sent. I think some timeout is what > eventually gets things going again (after about 30 seconds). Does that make > sense?" > > A possible patch is here: https://phabricator.kde.org/P385 could someone try > it? Nice to see that a patch's development is at least being kicked off. Dealing with this bug for more than a month now has been quite annoying. :P Too bad I don't know C++ (I'm learning software development in college though, so that's something I may learn in the future), because I could've helped with this problem as well. :( -- You are receiving this mail because: You are watching all bug changes.
