smithay: Anvil segfault on launch via --x11 on Debian
Running cargo run -- --x11 on Debian 11 gives a segfault with the below error:
Dec 20 10:08:34.379 INFO Starting anvil with x11 backend
Dec 20 10:08:34.379 INFO Connecting to the X server, smithay_module: backend_x11
Dec 20 10:08:34.380 INFO Connected to screen 0, smithay_module: backend_x11
Dec 20 10:08:34.380 INFO Loaded extension Present version 1.0, smithay_module: backend_x11
Dec 20 10:08:34.381 INFO Loaded extension XFIXES version 4.0, smithay_module: backend_x11
Dec 20 10:08:34.381 INFO Loaded extension DRI3 version 1.0, smithay_module: backend_x11
Dec 20 10:08:34.382 DEBG Supported EGL client extensions: ["EGL_EXT_device_base", "EGL_EXT_device_enumeration", "EGL_EXT_device_query", "EGL_EXT_platform_base", "EGL_KHR_client_get_all_proc_addresses", "EGL_EXT_client_extensions", "EGL_KHR_debug", "EGL_EXT_platform_device", "EGL_EXT_platform_wayland", "EGL_KHR_platform_wayland", "EGL_EXT_platform_x11", "EGL_KHR_platform_x11", "EGL_MESA_platform_gbm", "EGL_KHR_platform_gbm", "EGL_MESA_platform_surfaceless"], smithay_module: backend_egl
Segmentation fault
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 19 (6 by maintainers)
Thank you. I will ask the debian package maintainers if this is feasible for them, or else if not then at least backport the fix. Either way smithay is probably going to have a mesa > 21 requirement initially. If debian 11 won’t do either of the needed steps, it just won’t be a supported distro for smithay/cosmic-comp then.
That settles it then, if mesa 20.x is officially unsupported, smithay won’t make an attempt in supporting it. That is just not feasible from a maintenance perspective.
So Debian has to either update mesa (which seems to be the recommended solution, though potentially difficult with their conservative upgrade strategy) or manually backport the required fix.
In a nutshell, mesa 20.x is no longer supported and if you use mesa 20.x, that means you won’t benefit from any improvements made to the graphics stack since late 2020 and are likely to find issues.
If you distro ships a mesa release which is no longer supported, please ask your distro maintainers to upgrade to a supported stable version.
Mesa has a release calendar that shows you the upcoming versions and estimated date of their release. Only the last two point releases get stable updates (at the time of writing, these are 22.1 and 22.2). Mesa 20.3 was released in December 2020 and is no longer supported or updated. We recommend that users don’t use unsupported mesa releases due to lack of new hardware support, bug fixes, and compatibility. You are likely to encounter problems if you try to play newer than 2020 games and you will also get no HW acceleration for any HW that was launched since 2020, and poor support for HW which was launched near the end of 2020.
I am reaching out to debian 11 package maintainers for libegl-mesa, as well as the mesa3d project, to see where best this fix can be backported upstream. I’m not sure if mesa3d versions have lifespan or eol dates (I cannot find any), so maybe the fix belongs to mesa3d and debian 11 picks it up as an update; not sure so trying both to see what happens