It seems most machines with this crash are real machines. And most of those have an Nvidia driver installed. But Nvidia is not always present, sometimes the crash happens with radeon and sometimes with vmwgfx.
Another feature of the crash seems to be this log message: libEGL warning: egl: failed to create dri2 screen but often you won't notice it because gdm has detected the crash when attempting to launch a Wayland session and started a Xorg session instead. And so our incident reports mostly only show the Xorg session starting up by the time the crash is caught. That's some good news at least - the automatic recovery is kicking in and people who do have this crash might not even notice it. ** Changed in: mesa (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in 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() Status in Mesa: New Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 48~beta-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/29b4464c85e6349b307fd74e2fd50e3e047fbe64 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2101817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp