<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - KDE Konsole very slow scrolling with TearFree and QT graphics system native" href="https://bugs.freedesktop.org/show_bug.cgi?id=77436#c47">Comment # 47</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - KDE Konsole very slow scrolling with TearFree and QT graphics system native" href="https://bugs.freedesktop.org/show_bug.cgi?id=77436">bug 77436</a> from <a class="email" href="mailto:absorbb@gmail.com" title="Ildar Nurislamov <absorbb@gmail.com>"> Ildar Nurislamov</a> <pre>I saw all this commits and built driver after every bunch of them. No changes was noticed. [281306.077] (II) intel(0): [DRI2] Setup complete [281306.077] (II) intel(0): [DRI2] DRI driver: i965 [281306.077] (II) intel(0): [DRI2] VDPAU driver: i965 [281306.077] (II) intel(0): direct rendering: DRI2 DRI3 enabled [281306.090] (II) GLX: Initialized DRI2 GL provider for screen 0 I believe this means that DRI3 is enabled. I did more testing today: AccelMethod "uxa" and AccelMethod "none" still doing great here. TearFree "false" with sna is still produce huge delay in drawing actual frames. That is why i believe problem is not TearFree related. It just appears differently and without TearFree it is much more weird. Low framerate and hangs are common things but delay in drawing actual screen content while doing it with a quite smooth framerate is something i experience the first time in my entire PC usage practice. Some new observations: 1. Lag depends of amount of text drawn in Konsole. Maybe 2. Running Diablo 3 in parallel improves the situation. Amount of improvements depends on scene that opened in Diablo. If it is character menu - scrolling is almost smooth, if it is actual game results are mixed.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>