gnome-control-center crashed with SIGSEGV in g_variant_unref()

[davidetkarine]

gnome-control-center crashed when launching it

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: deja-dup 20.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CheckboxSubmission: 6cde8fb3bea14523ae6038abd43d9680
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
CrashCounter: 1
Date: Wed Sep 28 12:50:21 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
ProcCmdline: gnome-control-center
ProcEnviron:
 SHELL=/bin/bash
 LC_MESSAGES=fr_FR.UTF-8
 LANGUAGE=fr_FR:en
 LANG=fr_FR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fb7c2a08bd9 <g_variant_unref+9>: lock xadd %eax,0x24(%rdi)
 PC (0x7fb7c2a08bd9) ok
 source "%eax" ok
 destination "0x24(%rdi)" (0x00000024) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: deja-dup
StacktraceTop:
 g_variant_unref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_settings_get_string () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 deja_dup_convert_ssh_to_file () from /usr/lib/control-center-1/panels/libdeja-dup.so
 deja_dup_initialize () from /usr/lib/control-center-1/panels/libdeja-dup.so
 deja_dup_gui_initialize () from /usr/lib/control-center-1/panels/libdeja-dup.so
Title: gnome-control-center crashed with SIGSEGV in g_variant_unref()
UpgradeStatus: Upgraded to oneiric on 2011-09-28 (0 days ago)
UserGroups: adm admin cdrom dialout dip lpadmin netdev plugdev sambashare vboxusers
XsessionErrors: (gwibber-service:1960): libindicate-WARNING **: Menu being changed when the indicator is visible. Listeners will NOT be notified of this change.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #841937, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.