indicator-applet assert failure: indicator-applet: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.

[Leo]

Binary package hint: indicator-applet

Indicator-applet has crashed.

Extra information:
It happened at the time of a gnome desktop login.
I had installed indicator-applet-complete but had not added it to the panel.
I had uninstalled indicator-messages and indicator-application.
I have set Power Manager to always show an icon at the Notification Area.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: indicator-applet 0.3.6-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
AssertionMessage: indicator-applet: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.
CrashCounter: 1
Date: Sun Apr 4 18:28:06 2010
ExecutablePath: /usr/lib/indicator-applet/indicator-applet
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcCmdline: /usr/lib/indicator-applet/indicator-applet --oaf-activate-iid=OAFIID:GNOME_IndicatorApplet_Factory --oaf-ior-fd=28
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
Signal: 6
SourcePackage: indicator-applet
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 __assert_fail () from /lib/tls/i686/cmov/libc.so.6
 _XAllocID () from /usr/lib/libX11.so.6
Title: indicator-applet assert failure: indicator-applet: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video
XsessionErrors: (polkit-gnome-authentication-agent-1:6851): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #551210, 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.