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

[Graham Lucking]

I have two user accounts to test 12.04, administrator (Unity 3D) and standard user (Unity 2D). Over the last few days when using the Unity 3D account gnome-Settings-daemon has crashed usually just after log in and usually due to obsolete libraries. I use synaptic to upgrade the respective libraries. This happen about 2 hours ago and I upgrade the obsolete libraries. I have not reported this as a bug. The process said it was not possible to report it.

Just now I logged out of the Unity 3D account into the Unity 2D account and gnome-settings-daemon closed unexpectedly and I was allowed to make this bug report.

Synaptic indicates that Gnome-settings-daemon is the latest version - 3.2.2-0ubuntu5. It and the related files are not marked for upgrade.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.2.2-0ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-5.11-generic 3.2.0-rc5
Uname: Linux 3.2.0-5-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Thu Dec 22 16:13:05 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
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 2011-11-09 (43 days ago)
UserGroups:

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