[Bug 1712757] Re: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor:5:g_settings_schema_get_value:g_settings_schema_key_init:g_settings_get_value:g_settings_get_boolean:deja_dup_migrate_settings

** Changed in: deja-dup (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712757 Title: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-

[Bug 1712757] Re: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor:5:g_settings_schema_get_value:g_settings_schema_key_init:g_settings_get_value:g_settings_get_boolean:deja_dup_migrate_settings

There is currently a segfault in the glib-compile-schemas code in artful (bug #1711545) which can explain outdated schemas registers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712757 Title:

[Bug 1712757] Re: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor:5:g_settings_schema_get_value:g_settings_schema_key_init:g_settings_get_value:g_settings_get_boolean:deja_dup_migrate_settings

There is no real solution to those cases and as you said it shouldn't be an issue for most users, probably not worth coming up with an hackish workaround (and the issue is not specific to deja-dup). One other case of such reports is also an outdated schemas in /usr/local or such taking over the

[Bug 1712757] Re: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor:5:g_settings_schema_get_value:g_settings_schema_key_init:g_settings_get_value:g_settings_get_boolean:deja_dup_migrate_settings

So my best guess... is that deja-dup-monitor is being run (it starts 120s after login) while an upgrade is happening, before the gschemas are re-compiled but after the binaries are installed. That seems like a small window... But certainly possible. I imagine it won't happen during a release