deja-dup-monitor crashed with SIGSEGV in g_settings_backend_unsubscribe()

[Tim Gardner]

deja-dup-monitor crashed with SIGSEGV in g_object_unref()

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: deja-dup 20.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-13.20-generic 3.0.6
Uname: Linux 3.0.6+ x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Thu Oct 6 13:43:36 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110829.1)
ProcCmdline: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc7938bfb70: mov (%rdi),%rax
 PC (0x7fc7938bfb70) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: deja-dup
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? ()
Title: deja-dup-monitor crashed with SIGSEGV in g_object_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 g_settings_backend_unsubscribe (backend=0x0, name=0x0) at /build/buildd/glib2.0-2.30.0/./gio/gsettingsbackend.c:859
 g_settings_finalize (object=0x20534e0) at /build/buildd/glib2.0-2.30.0/./gio/gsettings.c:555
 g_object_unref (_object=0x20534e0) at /build/buildd/glib2.0-2.30.0/./gobject/gobject.c:2746
 deja_dup_initialize (header=0x0, msg=0x0) at CommonUtils.c:1326
 monitor_main (args_length1=1, args=0x7fffcc6d6328) at monitor.c:806

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Wolf Halton (saphil)]

If it matters, I am running this on a VMWare virtual machine

[Eliah Kagan (degeneracypressure)]

I've just reported bug 888209. I think it is the same bug as this, but I am not sure, because there are a couple of other steps in the stack trace.

[Michael Terry (mterry)]

This looks like a bug in glib2.0? Looks like the gsettings backend is NULL for some reason, which it doesn't handle well.