[xrandr]: gnome-settings-daemon crashed with signal 5 in _XReply()

[Jason Yang]

1) Clean VMWare Player install of 12.04
2) Upgraded to 12.10
3) Uninstalled unity via command:

sudo apt-get remove unity unity-2d unity-2d-panel unity-2d-spread unity-asset-pool unity-services unity-lens-files unity-lens-music unity-lens-applications gir1.2-unity-5.0 unity-common indicator-sound indicator-power indicator-appmenu libindicator7 indicator-application indicator-datetime indicator-messages libnux-2.0-0 nux-tools libunity-misc4 unity-2d-common

4) Install gnome3 with:

sudo add-apt-repository ppa:gnome3-team/gnome3
sudo apt-get update
sudo apt-get install gnome-shell

5) Tried to log in but the screen remains "blank" (nothing except the wallpaper) until something crashes and I am lead to submit this bug report.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-settings-daemon 3.4.2-0ubuntu13
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Mon Sep 24 03:21:41 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
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
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XRRSetCrtcConfig () from /usr/lib/x86_64-linux-gnu/libXrandr.so.2
 gnome_rr_crtc_set_config_with_time () from /usr/lib/libgnome-desktop-3.so.4
 ?? () from /usr/lib/libgnome-desktop-3.so.4
Title: [xrandr]: gnome-settings-daemon crashed with signal 5 in _XReply()
UpgradeStatus: Upgraded to quantal on 2012-09-24 (0 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 #907052, 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.