It's not an issue with the code but glib aborting on a missing schemas key (which is considered as a corrupted installation), the reasons can include - the schemas update failed - there is a local installation taking over the system schemas and outdated/not providing the key - could be that the program get started before the schemas cache has been updated (by its trigger), that's not likely though
It's not really easy to tell what's going on without having a reporter who hit the issue to provide details -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816410 Title: /usr/bin/update- manager:5:g_settings_schema_get_value:g_settings_schema_key_init:g_settings_get_value:g_settings_get_int:ffi_call_SYSV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1816410/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
