/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
Bug #1712757 reported by
errors.ubuntu.com bug bridge
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
deja-dup (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
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:/
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://
Changed in deja-dup (Ubuntu): | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
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 upgrade, thankfully.
I'm not sure whether this is worth trying to work around?