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

[Empty]

It happened when a remote client tried to connect this machine.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.2.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4
Uname: Linux 3.2.0-3-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Wed Dec 7 22:04:20 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
SegvAnalysis:
 Segfault happened at: 0x7f174edbf548 <gsd_power_manager_start+1720>: mov 0x8(%rax),%rcx
 PC (0x7f174edbf548) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 gsd_power_manager_start () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
 gnome_settings_plugin_info_activate ()
 _start ()
Title: gnome-settings-daemon crashed with SIGSEGV in gsd_power_manager_start()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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