<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - swrast: Epiphany WEB browser core dumps under Mesa 17.3.3" href="https://bugs.freedesktop.org/show_bug.cgi?id=104949#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - swrast: Epiphany WEB browser core dumps under Mesa 17.3.3" href="https://bugs.freedesktop.org/show_bug.cgi?id=104949">bug 104949</a> from <a class="email" href="mailto:wblaszcz@bigpond.net.au" title="Wayne Blaszczyk <wblaszcz@bigpond.net.au>"> Wayne Blaszczyk</a> <pre>(In reply to Daniel Stone from <a href="show_bug.cgi?id=104949#c3">comment #3</a>) > Yeah, good catch! Bug filed: <a href="https://bugs.webkit.org/show_bug.cgi?id=182490">https://bugs.webkit.org/show_bug.cgi?id=182490</a> I've applied the following patch to webkitgtk-2.18.6 <a href="https://bug-182490-attachments.webkit.org/attachment.cgi?id=333283">https://bug-182490-attachments.webkit.org/attachment.cgi?id=333283</a> Epiphany now starts fine with Mesa 17.3.3. But there is a difference in the warnings. Epiphany under Mesa 17.3.3 produces the following: WaylandCompositor requires eglBindWaylandDisplayWL, eglUnbindWaylandDisplayWL and eglQueryWaylandBuffer. Nested Wayland compositor could not initialize EGL Epiphany under Mesa 17.2.8 produces the following: WaylandCompositor requires eglCreateImage and eglDestroyImage. Nested Wayland compositor could not initialize EGL So, I guess it does get further in its initializeEGL method. Thanks.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>