gnome-settings-daemon crashed with signal 5 in _XReply()

[kyleabaker]

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
Description: Ubuntu precise (development branch)
Release: 12.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
gnome-settings-daemon:
  Installed: 3.2.2-0ubuntu10
  Candidate: 3.2.2-0ubuntu10
  Version table:
 *** 3.2.2-0ubuntu10 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.2.2-0ubuntu10
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0
Uname: Linux 3.2.0-8-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sun Jan 15 17:32:42 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XGetWindowAttributes () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XGetWindowAttributes () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: gnome-settings-daemon crashed with signal 5 in _XReply()
UpgradeStatus: Upgraded to precise on 2012-01-14 (1 days ago)
UserGroups: adm cdrom dip 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 #903973, 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.