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

[iMac]

This is #868928 however I have newer packages, so I let it retrace to see if something new showed up.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.2.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Tue Nov 29 09:45:33 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f002fdf6548 <gsd_power_manager_start+1720>: mov 0x8(%rax),%rcx
 PC (0x7f002fdf6548) 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: Upgraded to oneiric on 2011-10-28 (31 days ago)
UserGroups: adm admin cdrom dialout dip disk fax fuse libvirtd lpadmin mythtv netdev plugdev pulse pulse-access sambashare scanner tape vboxusers vde2-net video
XsessionErrors:
 (gwibber-service:2912): libindicate-WARNING **: Menu being changed when the indicator is visible. Listeners will NOT be notified of this change.
 (evolution:3274): camel-CRITICAL **: camel_session_add_service: assertion `uri_string != NULL' failed

[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.