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 package version
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1712757 Title: /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 Status in deja-dup package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding deja-dup. This problem was most recently seen with package version 35.5-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/5709e9321dbca261fbe04fa7c3be988a53d3f4da 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/deja-dup/+bug/1712757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
