deja-dup-monitor crashed with signal 7 in g_object_newv()

[Ralph Forbes]

 I think my problems were caused by using Bleachbit.

Ubuntu 12.04 LTS Beta 1

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: deja-dup 21.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
Date: Sun Mar 4 17:45:33 2012
ExecutablePath: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
ExecutableTimestamp: 1330022001
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
ProcCwd: /home/ralph
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 7
SourcePackage: deja-dup
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: deja-dup-monitor crashed with signal 7 in g_object_newv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 dconf_engine_refresh_user (engine=0x19bd2d0) at ../engine/dconf-engine.c:146
 dconf_engine_refresh (engine=0x19bd2d0) at ../engine/dconf-engine.c:197
 dconf_engine_get_state (engine=0x19bd2d0) at ../engine/dconf-engine.c:207
 outstanding_watch_new (name=0x19e77c0 "/org/gnome/deja-dup/", dcsb=0x19d3810) at dconfsettingsbackend.c:538
 dconf_settings_backend_subscribe (backend=<optimized out>, name=<optimized out>) at dconfsettingsbackend.c:626

[Launchpad Janitor (janitor)]

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

[Michael Terry (mterry)]

Not sure what to do with this. It crashes in dconf, so I'll re-assign there. But the stack doesn't look incomplete, so there might be some memory corruption.