gnome-shell crashed with SIGTRAP in g_logv("Settings schema 'org.gnome.desktop.privacy' does not contain a key named 'privacy-screen'") from glog() from g_settings_schema_get_value() from g_settings_schema_get_value() from g_settings_schema_key_init() from g_settings_get_value() from g_settings_get_boolean()

Looking to some of the error reports, some have that in their journal

systemd[1043]: <email address hidden>: Failed with result 'exit-code'.
gnome-shell[2350]: Settings schema 'org.gnome.desktop.peripherals.keyboard' does not contain a key named 'remember-numlock-state'
systemd[1043]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP

where 'gsettings-desktop-schemas 3.34.0-1ubuntu1'

or

gnome-session-binary[2189]: WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' killed by signal 5
gsd-media-keys[2311]: Settings schema 'org.gnome.settings-daemon.plugins.media-keys.deprecated' is not installed
systemd[1034]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP

It's the old 'gsettings abort when schemas/keys are missing', the e.u.c reports don't include a procmaps or enough informations to tell what's going on exactly but it's likely that either the schemas cache update failed or is taken over by a /usr/local/ version or similar which is outdated/doesn't include the new key

Likely an installation/local problem more than a gnome-shell issue, unsure if we should close the report?

If this, 'gsettings abort when schemas/keys are missing', is a class of crash which is not valuable can we prevent reporting them in the apport package hook or in apport in general?

On Wed, Oct 30, 2019 at 05:22:05PM -0000, Brian Murray wrote:
> If this, 'gsettings abort when schemas/keys are missing', is a class of
> crash which is not valuable can we prevent reporting them in the apport
> package hook or in apport in general?

It is valuable if it's pointing to a bug in the distribution, for
example a missing dependency on a package providing a schema.

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]

One thing we discussed with Marco a bit earlier is that it would be nice of apport included some flag if the gsettings cache was coming from /usr/local which is a common cause for reports like this one

Zero reports in 20.04 since it was released with 3.36.

This looks like a catch-all bug where errors.ubuntu.com will bunch unrelated crashes together because they have similar stack traces.

Bah, recent mutter depends on newer gsettings schema, there's not really much we can to avoid this.

Unless someone had wrong upgrades?