[power]: gnome-settings-daemon crashed with SIGSEGV when opening chrome

[vc4543]

1) lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

2) apt-cache policy gnome-settings-daemon
gnome-settings-daemon:
  Installed: 3.4.0-0ubuntu3
  Candidate: 3.4.0-0ubuntu3
  Version table:
 *** 3.4.0-0ubuntu3 0
        500 http://se.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

3) use chrome, it did open but the crqash dialog appeared
4) chrome appeared on choosing the menu option. but a crash dialog also appeared.
    I dont know if its because i open chrome, a race condition or just part of a parallel process that read settings.

Additional..
I can help if someone guide me through. Should I download sources (gnome-settings-daemon) and make an install?

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.4.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13
Uname: Linux 3.2.0-21-generic-pae i686
NonfreeKernelModules: wl nvidia
ApportVersion: 2.0-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Wed Apr 4 08:21:18 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Beta i386 (20120229)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
Title: [power]: gnome-settings-daemon crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo

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