Unable to run latest master on Debian 12

Output:

QA Timing INIT: 000696ms
RBDOOM 3 BFG 1.6.0 preview.1403 linux-x86_64 Sep  4 2024 18:23:27
file system initialized.
--------------------------------------
WARNING: Unable to open resource file maps/_startup.resources
WARNING: Unable to open resource file maps/_startup.resources
----- Initializing Decls -----
------------------------------
Couldn't open journal files
/proc/cpuinfo CPU processors: 8
/proc/cpuinfo CPU logical cores: 8
execing default.cfg
execing D3BFGConfig.cfg
couldn't exec autoexec.cfg
----- R_InitOpenGL -----
r_vidMode reset from 11 to 0.
Initializing Vulkan subsystem
Enabled Vulkan instance extensions:
    VK_EXT_debug_report
    VK_KHR_xlib_surface
    VK_KHR_surface
    VK_KHR_get_physical_device_properties2
Enabled Vulkan layers:
WARNING: Error while creating SDL Vulkan surface: VK_KHR_xlib_surface extension is not enabled in the Vulkan instance.
Unknown command 'vid_restart'
Sys_Error: Failed to create a Vulkan window surface, error code = VK_ERROR_SURFACE_LOST_KHR

Debian 12, x11: vulkaninfo.txt

How are you running the game (wine/compiled)?

I just compiled the source on Debian 12 and moved the base directory and the executable to my doom3 directory. I have been playing without a problem (with NVIDIA's proprietary drivers).

I found this error and a patch here: https://forums.developer.nvidia.com/t/doom-3-bfg-vulkan-renderer-running-on-nvidia-jetson-nano/120549/4

Compiled from latest master, running on a RTX 2060 with the proprietary drivers version 535.183.01. Using X11, not Wayland.

I did check that patch and manually added the VK_KHR_xlib_surface extension the SDL extension list when creating the vector, but that did not fix the issue:

RBDOOM-3-BFG/neo/sys/sdl/sdl_vkimp.cpp

Line 63 in 747878e

std::vector<const char*> sdlInstanceExtensions = {};

I'm using the latest 560 driver: https://www.nvidia.com/en-us/geforce/drivers/results/230918/
Don't know if that's going to help, though.

Did you copy the source base directory to your game directory?
If you like I can upload my executable.

Yeah, everything runs fine on 1.4.0, which is the latest tag without NVRHI. Definitely Vulkan-related, and probably X11?

Appreciate the help, though!

These are my installed vulkan packages:

$ aptitude search vulkan | grep ^i
i  libvulkan-dev - Vulkan loader library -- development files
i  libvulkan1 - Vulkan loader library
i  libvulkan1:i386 - Vulkan loader library
i  mesa-vulkan-drivers - Mesa Vulkan graphics drivers
i  mesa-vulkan-drivers:i386 - Mesa Vulkan graphics drivers
i  vulkan-tools - Miscellaneous Vulkan utilities