[Webkit-unassigned] [Bug 263208] New: [GTK] Web inspector does not render anything: Failed to create GBM device for render device: /dev/dri/renderD128: No such file or directory
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Oct 16 12:43:37 PDT 2023
https://bugs.webkit.org/show_bug.cgi?id=263208
Bug ID: 263208
Summary: [GTK] Web inspector does not render anything: Failed
to create GBM device for render device:
/dev/dri/renderD128: No such file or directory
Product: WebKit
Version: WebKit Nightly Build
Hardware: All
OS: All
Status: NEW
Severity: Normal
Priority: P2
Component: WebKitGTK
Assignee: webkit-unassigned at lists.webkit.org
Reporter: mcatanzaro at redhat.com
CC: bugs-noreply at webkitgtk.org
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?
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20231016/85e30e57/attachment.htm>
More information about the webkit-unassigned
mailing list