Using Epiphany Tech Preview with WebKitGTK 2.42.1, I notice the web inspector occasionally breaks and fails to render anything. When this happens, I see the following scary errors in my journal: Oct 16 14:35:44 chargestone-cave org.gnome.Epiphany.Devel.desktop[111657]: Failed to create GBM device for render device: /dev/dri/renderD128: No such file or directory Oct 16 14:35:44 chargestone-cave org.gnome.Epiphany.Devel.desktop[111657]: Cannot get default EGL display: EGL_BAD_PARAMETER Oct 16 14:35:44 chargestone-cave org.gnome.Epiphany.Devel.desktop[111657]: Cannot create EGL context: invalid display (last error: EGL_SUCCESS) I wonder why is it trying to open a render device that doesn't exist? That device actually *does* exist inside the flatpak sandbox of the broken Epiphany instance: $ flatpak enter org.gnome.Epiphany.Devel ls /dev/dri by-path card1 renderD128 Maybe it's not accessible inside the flatpak-spawn subsandbox?
Still broken in WebKitGTK 2.43.3. The web inspector works fine in a freshly-launched Epiphany. I think it breaks only after Epiphany has been open for a while.
Dunno if related or not, here the inspector server is broken. When i click on a target to inspect, the window opens but nothing renders, there is a webview (mouse cursor changes) when i move the mouse around in that window, but nothing renders. In journal: Failed to create GBM buffer of size 0x0: Invalid argument
(In reply to Philippe Normand from comment #2) > Failed to create GBM buffer of size 0x0: Invalid argument That one is bug #265154
Still broken. I noticed this again today using 2.44.2 in Ephy Tech Preview.