Logout hang with geyes on the panel

[Arvind S N <arvind samptur wipro com>]

Hi,
On a logout or removing panel using gnome-session-properties with geyes
present causes a hang (geyes crashes). With setting
GNOME_DISABLE_CRASH_DIALOG the following is seen on the terminal
geyes_applet is run.

(geyes_applet2:10684): Gdk-CRITICAL **: file gdkmain-x11.c: line 672
(gdk_error_trap_pop): assertion `gdk_error_traps != NULL' failed

Gdk-ERROR **: The program 'geyes_applet2' received an X Window System
error.
This probably reflects a bug in the program.
The error was 'BadGC (invalid GC parameter)'.
  (Details: serial 183515 error_code 13 request_code 60 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error()
function.)
aborting...
Aborted (core dumped)

The trace would point to a timer function in geyes applet which keeps
rendering with a timeout of 75 msecs.

On Michael's advice, I tried some tests on the gtk+/tests/testsocket.c.
Add a timer function with a timeout of 75 msecs to the socket created.
All that the function contained was a  printf ("Hello");. Kept
continuously adding an active child, in the meanwhile killed the
lt-testsocket process, and saw the following on the terminal.

(lt-testsocket_child:5855): Gdk-WARNING **: GdkWindow 0x6000003
unexpectedly destroyed


Gdk-ERROR **: The program 'lt-testsocket_child' received an X Window
System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 1416 error_code 9 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error()
function.)
aborting...


Is this bug supposed to be handled by ignoring the BadGC error condition
in bonobo_x_error_handler method in libbonoboui/bonobo/bonobo-ui-main.c
which is currently ignoring BadDrawable or a BadWindow or are we having
problems with GtkSocket/GtkPlug which need to be fixed.

Please let know your thoughts.

-Arvind

PS: The buggzilla id is http://bugzilla.gnome.org/show_bug.cgi?id=90547