Here's what we already know: The bug triggers when Zink fails to find a working Vulkan driver for a known-supported device. This was worked around by Daniel's patch, and more recently fixed upstream in a similar way, so that we can fall back to llvmpipe rather than crashing when trying Zink.
Given what we know, here's my two unverified hypothesis of what might be wrong with NVIDIA: * Secure-boot is enabled and the NVIDIA drivers are installed but not signed. This implies using the DKMS modules rather than the Canonical-signed modules, and it is the default for `apt install nvidia-driver-XXX`. The nouveau kernel module is disabled in modprobe, and the nvidia kernel module fails to load, so we're left with no working driver. * The NVIDIA kernel modules are installed and loaded, but the userspace libraries are not. I'm not sure how this would happen, but you could for example manually install the `nvidia-dkms-570` rather than the top-most nvidia-driver-570 metapackage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2101817 Title: gnome-shell crashed with SIGSEGV in drisw_init_screen() from driCreateNewScreen3() from dri2_create_screen() from dri2_initialize_device() from dri2_initialize() To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2101817/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
