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

[Wanderson]

This bug impact the Ubuntu 11.10 amd64 version

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.2.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Sep 28 19:09:03 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7ff1a5eeca96: mov 0x10(%rdx),%rdx
 PC (0x7ff1a5eeca96) 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-28 (0 days ago)
UserGroups:

XsessionErrors:
 (gnome-settings-daemon:5934): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed
 (bluetooth-applet:5962): Gdk-WARNING **: bluetooth-applet: Fatal IO error 11 (Recurso temporariamente indisponível) on X server :1.
 (nautilus:5965): Gdk-WARNING **: The application 'nautilus' lost its connection to the display :1;

[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 #861245, 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.