<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Weston-desktop-shell hangs." href="https://bugs.freedesktop.org/show_bug.cgi?id=74752#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Weston-desktop-shell hangs." href="https://bugs.freedesktop.org/show_bug.cgi?id=74752">bug 74752</a> from <a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> Pekka Paalanen</a> <pre>(In reply to <a href="show_bug.cgi?id=74752#c7">comment #7</a>) > I forgot to mention, I am compiling Weston with --with-cairo=gl Ookay, that's pretty rare I think. Do wayland clients use egl_dri2 or egl_gallium in your system? Fbdev backend does not initialize server-side EGL, so it does not advertise wl_drm. DRM and x11 backends do. This means that on client side, weston-desktop-shell on fbdev-compositor will either complain and fall back to wl_shm, or it will use egl_gallium with a software renderer, depending on your Mesa build. On the other compositors, weston-desktop-shell will attempt to use wl_drm if advertized, which means you hit either egl_dri2 or egl_gallium, again depending on your Mesa build. What is your gfx card flavour, intel, nouveau or radeon? I believe the untested and mostly unmaintained combination is egl_gallium with nouveau and radeon drivers (with wl_drm), so problems are not unexpected. Do you hit this case? Unfortunately egl_gallium is atm the only way to use software rendered GL, and Mesa prefers egl_gallium over egl_dri2. You could override that with EGL_DRIVER env var.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>