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?
** Changed in: deja-dup (Ubuntu)
Importance: Undecided => Medium
** Changed in: deja-dup (Ubuntu)
Status: New => Confirmed
--
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-
monitor:5:g_settings_schema_get_value:g_settings_schema_key_init:g_settings_get_value:g_settings_get_boolean:deja_dup_migrate_settings
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1712757/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
