Zero reports in 20.04 since it was released with 3.36.
** Changed in: gnome-shell (Ubuntu)
Status: New => Fix Released
--
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/1850214
** Tags removed: disco
--
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/1850214
Title:
gnome-shell crashed with SIGTRAP in g_settings_schema_get_value() from
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
--
You received this bug notification because you are a member of Desktop
Packages, which is
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?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Looking to some of the error reports, some have that in their journal
systemd[1043]: gnome-session-manager@gnome-login.service: Failed with result
'exit-code'.
gnome-shell[2350]: Settings schema 'org.gnome.desktop.peripherals.keyboard'
does not contain a key named 'remember-numlock-state'
** Summary changed:
-
/usr/bin/gnome-shell:5:g_settings_schema_get_value:g_settings_schema_get_value:g_settings_schema_key_init:g_settings_get_value:g_settings_get_boolean
+ gnome-shell crashed with SIGTRAP in g_settings_schema_get_value() from
g_settings_schema_get_value() from
6 matches
Mail list logo
