nautilus crashed with signal 5 in _XReadEvents()

[Casey McMullen]

Got this error immediately after logging in, before doing anything else.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu2
Architecture: amd64
Date: Wed Oct 10 18:10:10 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1101x689+2116+138'"
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReadEvents () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XIfEvent () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 gdk_x11_get_server_time () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: nautilus crashed with signal 5 in _XReadEvents()
UpgradeStatus: Upgraded to quantal on 2012-09-26 (14 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers www-data
XsessionErrors:
 (nautilus:2226): Gdk-ERROR **: The program 'nautilus' received an X Window System error.
 The error was 'BadPixmap (invalid Pixmap parameter)'.
   (Details: serial 633 error_code 4 request_code 2 minor_code 0)
 (gtk-window-decorator:2521): GLib-CRITICAL **: g_hash_table_remove_internal: assertion `hash_table != 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 #965024, 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.