That's something may have happened, but it's weird that a restart could lead to load a not-yet configured new gnome-shell (as its dependency has not been configured yet).
So, that's definitely a quite weird problem. It seems more packaging related, but g-s is correctly depending on the right version of desktop schemas. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2084761 Title: gnome-shell crashes with SIGTRAP ("Settings schema 'org.gnome.desktop.interface' does not contain a key named 'accent- color'") Status in gnome-shell 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 47.0-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/a244eec3c4a760a463be275e323b2717661e947e 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/ubuntu/+source/gnome-shell/+bug/2084761/+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
