Date: Tue, 05 May 2020 13:04:55 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 246220] graphics/wayland: wayland-egl: could not open /dev/dri/renderD Message-ID: <bug-246220-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246220 Bug ID: 246220 Summary: graphics/wayland: wayland-egl: could not open /dev/dri/renderD Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: x11@FreeBSD.org Reporter: lantw44@gmail.com Assignee: x11@FreeBSD.org Flags: maintainer-feedback?(x11@FreeBSD.org) I don't know where the bug came from. If I chose the wrong port, please mov= e it to the correct one. I was trying to run mutter as a nested Wayland compositor under Xorg, and I found Xwayland just showed an error and hung. It could not show any X11 win= dow. wayland-egl: could not open /dev/dri/renderD (No such file or directory) There is no /dev/dri/renderD on the system, and I don't know why it wants t= he file. Running eglinfo also shows the same error: libEGL warning: wayland-egl: could not open /dev/dri/renderD (No such file = or directory) It seems to be a problem of the Wayland compositor, except that it isn't limited to a single Wayland compositor implementation. Both mutter and sway have the same issue. Sometimes they even report errors with weird names suc= h as /dev/dri/renderDvblank_mode and /dev/dri/renderDbo_reuse. If I create the symlink /dev/dri/renderD -> renderD128, Xwayland can work properly. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-246220-7788>