Kyle Brenneman

> The only reference I can find for eglGetPlatformDisplay to return `EGL_BAD_ATTRIBUTE` is noted in the `EGL_EXT_explicit_device` extension notes `EGL_BAD_ATTRIBUTE` is a generic error for any case where the implementation...

I think I know what the problem is here. In `wlEglGetConfigAttribHook` and `wlEglChooseConfigHook`, it tweaks driver's attribute list to add EGL_WINDOW_BIT, but it needs to also tweak EGL_MIN_SWAP_INTERVAL and EGL_MAX_SWAP_INTERVAL...

There isn't a separate libglvnd package, but packaging script for nvidia-384 includes the libglvnd libraries that are included in the .run installer. Since 16.04 doesn't have a libglvnd package or...

On a related note, I've got a patch for the nvidia-410/415/418/430 packages in the graphics-drivers PPA, but I don't know where those are hosted.

Is there a reason for using the non-libglvnd version specifically? From a packaging standpoint, they're basically interchangeable.

Can you be more specific about what you're trying to run, and what it's doing? A VM is going to provide its own virtualized graphics device, so nothing running in...

@RyzenDew - What distro, which version of the driver, which version of EGL-Wayland, and which compositor are you using? Messages from KHR_EGL_debug would probably be useful, too, since the Boxes...

Yeah, anything with Flatpak would need an update to its runtime environment to pick up an updated egl-wayland library. It might be possible to work around that by using `flatpak...

Now that I think about it, if an application calls `eglGetDisplay(NULL)`, or `eglGetPlatformDisplay` with `EGL_PLATFORM_DEVICE_EXT` or `EGL_PLATFORM_SURFACELESS_MESA` then that would also cause the NVIDIA GPU to wake up. All of...

> That indeed makes sense, I assume in these cases we'd need to create the relevant issue reports for those projects separately since this is out of egl-wayland's hands? Most...