[background]: gnome-control-center crashed with SIGSEGV in ffi_call_SYSV()

[Matthew Paul Thomas]

.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu4
Architecture: i386
Date: Wed Apr 18 09:48:50 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: gnome-control-center --overview
SegvAnalysis:
 Segfault happened at: 0xadc6ded: mov (%eax),%eax
 PC (0x0adc6ded) ok
 source "(%eax)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/control-center-1/panels/libbackground.so
 ?? () from /usr/lib/control-center-1/panels/libbackground.so
 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic_va (closure=0xa490f8f0, return_value=0x0, instance=0x21347c60, args_list=0xbfda753c "\220H\027!", marshal_data=0x0, n_params=3, param_types=0x20f43e18) at /build/buildd/glib2.0-2.32.1/./gobject/gclosure.c:1550
Title: [background]: gnome-control-center crashed with SIGSEGV in ffi_call_SYSV()
UpgradeStatus: Upgraded to precise on 2012-02-27 (50 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup 22.0-0ubuntu2
 gnome-bluetooth 3.2.2-0ubuntu5
 indicator-datetime 0.3.94-0ubuntu1

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #976165, 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.