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

[Julian Brelsford]

i just "logged out" from a gnome-3-fallback session, which uses gnome-panel. When I logged back in to a Xubuntu session, i found that a bug report was waiting to be sent

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-panel 1:3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-2.6-generic 3.2.0-rc3
Uname: Linux 3.2.0-2-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
AssertionMessage: gnome-panel: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.
Date: Sat Dec 3 09:55:24 2011
ExecutablePath: /usr/bin/gnome-panel
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.3)
ProcCmdline: gnome-panel
Signal: 6
SourcePackage: gnome-panel
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 __assert_fail () from /lib/i386-linux-gnu/libc.so.6
 _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: gnome-panel assert failure: gnome-panel: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.
UpgradeStatus: Upgraded to precise on 2011-09-30 (64 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 __GI___assert_fail (assertion=0x1074419 "ret != inval_id", file=0x107438a "../../src/xcb_io.c", line=528, function=0x107449e "_XAllocID") at assert.c:81
 _XAllocID (dpy=0x89b53f0) at ../../src/xcb_io.c:528
 XCreatePixmap (dpy=0x89b53f0, d=16788080, width=22, height=22, depth=32) at ../../src/CrPixmap.c:56
 _cairo_xlib_surface_create_similar (abstract_src=0xaa12aea8, content=CAIRO_CONTENT_COLOR_ALPHA, width=22, height=22) at /build/buildd/cairo-1.10.2/src/cairo-xlib-surface.c:393
 _cairo_surface_create_similar_scratch (other=0xaa12aea8, content=CAIRO_CONTENT_COLOR_ALPHA, width=22, height=22) at /build/buildd/cairo-1.10.2/src/cairo-surface.c:461

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.