> Secure-boot is enabled and the NVIDIA drivers are installed but not signed.
I see kernel messages in peoples' logs suggesting that's the case fairly regularly. Also I get the impression our list of kernel versions for which Canonical has signed modules is too small. Not just because some people have custom kernels, but they might have enabled Nvidia through Additional Drivers and not yet be up to date with the latest kernel update (which I assume Additional Drivers does not fix). So the signed module they require used to exist but isn't offered by updates anymore. It just occurs to me now that I probably never encounter problems with DKMS because I leave my development desktop with Secure Boot disabled. Thanks for the reminder. -- You received this bug notification because you are a member of Ubuntu Touch seeded 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: Fix Released 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
