nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.

[jalpesh]

Had not performed any action yet. Am running in cairo-dock session with gnome and effects in ubuntu 12.04.

Description: Ubuntu precise (development branch)
Release: 12.04

nautilus:
  Installed: 1:3.2.1-2ubuntu4
  Candidate: 1:3.2.1-2ubuntu4
  Version table:
 *** 1:3.2.1-2ubuntu4 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main i386 Packages

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.2.1-2ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-11.49-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: i386
AssertionMessage: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.
Date: Tue Dec 27 15:50:03 2011
DuplicateOf: https://bugs.launchpad.net/bugs/905686
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 __GI___assert_fail (assertion=0xed8419 "ret != inval_id", file=0xed838a "../../src/xcb_io.c", line=528, function=0xed849e "_XAllocID") at assert.c:81
 _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6
 XCreatePixmap () from /usr/lib/i386-linux-gnu/libX11.so.6
 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2
 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2
Title: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.
UpgradeStatus: Upgraded to precise on 2011-12-22 (5 days ago)
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare vboxusers

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