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

[Kyle Raglin]

Binary package hint: gnome-panel

simply logged in

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-panel 1:2.30.2-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
AssertionMessage: gnome-panel: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.
Date: Wed Sep 22 21:58:34 2010
ExecutablePath: /usr/bin/gnome-panel
GConfNonDefault:
 /apps/panel/general/applet_id_list=[fast_user_switch_screen0,trashapplet_screen0,indicator_applet_screen0,notification_area_screen0,clock_screen0,applet_0,applet_2,applet_4]
 /apps/panel/general/object_id_list=[yelp_launcher_screen0,browser_launcher_screen0,menu_bar_screen0,object_0,object_1,object_2,object_3]
 /apps/panel/general/toplevel_id_list=[bottom_panel_screen0,top_panel_screen0]
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: gnome-panel
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-panel
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/libc.so.6
 abort () from /lib/libc.so.6
 __assert_fail () from /lib/libc.so.6
 _XAllocID () from /usr/lib/libX11.so.6
Title: gnome-panel assert failure: gnome-panel: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
XsessionErrors:
 (polkit-gnome-authentication-agent-1:5498): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (bluetooth-applet:5496): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' 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 #642784, 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.