Comment 10 for bug 1805444

Daniel van Vugt (vanvugt) wrote :

Fact is stranger than fiction. I failed to consider that maybe EGLStreams was working in mutter 3.28 and it got broken later on. Actually there were TWO separate regressions (separate to this bug) this year. So here are corrections to comment #8 after a more detailed analysis:

mutter 3.28.3 in 18.04:
  * EGLDevice configured, compiled, but not working (this bug)
  * EGLStreams not configurable, always built, but also not working (this bug)

mutter 3.28.4 (prerelease):
  * EGLDevice compiled and working
  * EGLStreams not configurable, always built, and working**

mutter 3.30.2 in 18.10 & 19.04:
  * EGLDevice compiled and working
  * EGLStreams' new build deps are missing so not configured, but compiled in anyway by accident because the new build deps were weak, and it's working**

mutter 3.32 (prerelease) from upstream git:
  * EGLDevice compiled and working
  * EGLStreams' new build deps are missing so not configured, and not compiled any more thanks to a recent "fix" 417c00b8fa. We can get the missing build deps either with libnvidia-egl-wayland-dev (soon-to-be in 19.04), or do some kind of revert of 417c00b8fa (because the new build deps are pretty weak and probably shouldn't have been implemented that way in mutter 3.30+).

** EGLStreams working means Wayland clients get full Nvidia acceleration but I thought it was broken for a while because that also includes 100% CPU use by [kworker/u16:3+events_unbound]. Possible driver bug?