Panel crashes (CVS 12/16 17:00) -- gtk+ bug?

[Jason Tackaberry <tack dok org>]

Today I have checked out the GNOME_STABLE branch of the gnome-libs and
gnome-core modules.  I rebuilt all the modules I use (glib, gtk+, imlib,
gtk-engines, ORBit, gnome-libs, and gnome-core) as of 12/16 17:00 (but we
all know how lagged anoncvs is).

Since the goal now is debugging, you'll probably hear a lot of from me. :) 
Here is the first: panel sigsegvs when I click on the GNOME menu.
It outputs:

Message: [26274] returning buffer 0x80b1268 from recv_reply
Message: [26279] returning buffer 0x80861c8 from recv_reply
Message: [26279] returning buffer 0x80861c8 from recv_reply
Message: [26279] returning buffer 0x80861c8 from recv_reply
Message: [26279] returning buffer 0x80861c8 from recv_reply
Message: [26279] returning buffer 0x80861c8 from recv_reply

SOCKET XID: 30002F4

Message: [26279] returning buffer 0x80861c8 from recv_reply
register ext: 8133D18
register ext->info: 8134318
add callback ext: 8133D18
Here!
add 0x3c00004
remove 0x3c00004
remove 0x3c00004

Gdk-ERROR **: BadWindow (invalid Window parameter)
  serial 2061 error_code 3 request_code 10 minor_code 0

aborting...
Aborted (core dumped)

gdb session:

Program received signal SIGSEGV, Segmentation fault.
0x402d586a in gtk_label_expose (widget=0x80e7470, event=0xbffff598)
    at gtklabel.c:881
881 if (GTK_WIDGET_VISIBLE (widget) && GTK_WIDGET_MAPPED (widget) &&
(gdb) bt
#0  0x402d586a in gtk_label_expose (widget=0x81349c4, event=0xbffff598)
    at gtklabel.c:881
#1  0x403429fd in gtk_marshal_BOOL__POINTER () at gtkmarshal.c:508
#2  0x40309b61 in gtk_signal_real_emit (object=0x81349c4, signal_id=31,
    params=0xbffff2cc) at gtksignal.c:1463
#3  0x40307d35 in gtk_signal_emit () at gtksignal.c:228
#4  0x4033a7d8 in gtk_widget_event () at gtkwidget.c:2501
#5  0x4033e73b in gtk_widget_real_draw (widget=0x81349c4, area=0x80ebf20)
    at gtkwidget.c:4376
#6  0x40342c1d in gtk_marshal_NONE__POINTER () at gtkmarshal.c:508
#7  0x40309a03 in gtk_signal_real_emit (object=0x81349c4, signal_id=14,
    params=0xbffff64c) at gtksignal.c:1411
#8  0x40307d35 in gtk_signal_emit () at gtksignal.c:228
#9  0x40339798 in gtk_widget_draw () at gtkwidget.c:2147
#10 0x403394df in gtk_widget_idle_draw (data=0x0) at gtkwidget.c:2126
#11 0x400b14cb in g_idle_dispatch (source_data=0x813e6a8,
    current_time=0xbffff9b0, user_data=0x0) at gmain.c:833
#12 0x400b0980 in g_main_dispatch (current_time=0xbffff9b0) at gmain.c:364
#13 0x400b0d66 in g_main_iterate (block=1, dispatch=1) at gmain.c:518
#14 0x400b0e49 in g_main_run () at gmain.c:525
#15 0x402de339 in gtk_main () at gtkmain.c:410
#16 0x8051b1d in main (argc=1, argv=0xbffffb44) at main.c:180

In fact other gtk+ apps give me this exact error, so this seems like a
gtk+ bug.  Probably a real stupid one too. :)

Jason.