<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Xwayland needs better Present extension support" href="https://bugs.freedesktop.org/show_bug.cgi?id=99702#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Xwayland needs better Present extension support" href="https://bugs.freedesktop.org/show_bug.cgi?id=99702">bug 99702</a> from <a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> Pekka Paalanen</a> <pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=99702#c7">comment #7</a>) > (In reply to Pekka Paalanen from <a href="show_bug.cgi?id=99702#c5">comment #5</a>) > > Btw. I'm not quite sure, but it might be so that Weston sends > > wl_buffer.release events too early for buffers that were directly scanned > > out with KMS. > > Given that Xwayland currently only ever uses a single buffer, are there any > wl_buffer.release events involved? Wait, it does that with EGL-based buffers too? Even though fullscreen EGL/GLX X11 clients use double or more buffering? I thought it only did it with wl_shm buffers. Or, only when not able to scan out from X11 client buffers? Can that ever even happen btw.? I thought it could, but maybe that's just NVIDIA stuff then? Or does it require an X11 compositing manager to actually set up the direct scanout by... fiddling with pixmaps or something? If that's true, then I don't think there should be any wl_buffer.release events being sent, but if one were to implement double-buffering or more in Xwayland, then there would be, and then you might see this issue. I meant this comment more as future note anyway, since fixing things in Xwayland might cause unexpected results - this could be one explanation.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>