[Bug 1816410] Re: /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

[Sebastien Bacher]

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
Foundations Bugs, which is subscribed to update-manager in 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

Status in update-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager.  This problem was most recently seen with package version 1:18.04.11.9, the problem page at https://errors.ubuntu.com/problem/9ee1f897702ad1792e5767a67b7d2c5fa193173c 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/update-manager/+bug/1816410/+subscriptions