gnome-settings-daemon crashed with SIGSEGV in g_simple_async_result_complete()

[Mauricio Pretto]

.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 27 16:39:34 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110919)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
SegvAnalysis:
 Segfault happened at: 0x7f747e69ca96: mov 0x10(%rdx),%rdx
 PC (0x7f747e69ca96) ok
 source "0x10(%rdx)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libxrandr.so
 g_simple_async_result_complete () 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_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-settings-daemon crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: Upgraded to oneiric on 2011-09-26 (0 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 on_bus_gotten (source_object=<optimized out>, res=<optimized out>, manager=0x1fb9980) at gsd-xrandr-manager.c:2078
 g_simple_async_result_complete (simple=0x1fb9920) at /build/buildd/glib2.0-2.30.0/./gio/gsimpleasyncresult.c:749
 complete_in_idle_cb (data=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gio/gsimpleasyncresult.c:761
 g_main_dispatch (context=0x1f2c6e0) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:2441
 g_main_context_dispatch (context=0x1f2c6e0) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3011

[Launchpad Janitor (janitor)]

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