Bug #1712757 reported by errors.ubuntu.com bug bridge on 2017-08-24
This bug affects 8 people
Affects Status Importance Assigned to Milestone
deja-dup (Ubuntu)

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/.

Michael Terry (mterry) wrote :

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
status: New → Confirmed
Sebastien Bacher (seb128) wrote :

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

Sebastien Bacher (seb128) wrote :

There is currently a segfault in the glib-compile-schemas code in artful (bug #1711545) which can explain outdated schemas registers

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers