GNOME Shell (Wayland) reports failed to create EGL context

Desktop
,
1

Hi Team,

We’re working on enabling GNOME-Wayland on Ubuntu 22.04 with our RISC-V64 Development Platform. We’re successfully able to bring up GNOME-Wayland Environment with GPU Hardware Acceleration support using our Imagination PowerVR GPU which supports OpenGL-ES 3.2. And we’re able to perform necessary windowing and other application usages as well. But one think we noticed with out usage is we encountered error logs within our JournalCtl for EGL (“Failed to make EGL context current with GL”) as below:

Ubuntu-riscv64 org.gnome.Shell.desktop[1270]: libEGL warning: DRI2: failed to rebind the previous context
Ubuntu-riscv64 org.gnome.Shell.desktop[1270]: Failed to make EGL context current with GL

We notice this error messages during each boot time upon GNOME Login. Which is suggested to be reported from GNOME Desktop Shell, Although we’re not exactly sure about want this issue is. It would be really helpful if we get some suggestions or help on fixing this issue.

System Windowing Environment:

  • GNOME Shell: 42.9

  • Mutter: 42.9-0ubuntu1

  • Distribution: Ubuntu 22.04 (Jammy)

  • Session type: Wayland

  • GPU: Imagination PowerVR (OpenGL ES 3.2 only, no desktop OpenGL)

  • EGL implementation: Mesa 22.3.5 + PowerVR driver

  • Kernel: 5.10.41

Any support or help would be highly appreciated, thank you!

Regards,

Sharan

1 Like
2

Searching for that warning leads me to glamor in Xwayland. Do you get hardware acceleration in X11 clients?

3

Hi @jadahl ,

Yes, we are noticed glamor initialized with GPU harware acceleration on X11, however this issue is focused more into GNOME wayland.

Let us know your thoughts on this.

Thanks.

4

What I mean that the log entries are coming from Xwayland, not gnome-shell. Note that it’s gnome-shell that launches Xwayland, and that is probably why it looks like it’s coming from gnome-shell, but I’m guessing it’s stdout/stderr forwarding that causes that.