[Uim] uim-toolbar-gtk-systray crashes when systray quits

[Etsushi Kato]

On 1/6/07, d+uim at vdr.jp <d+uim at vdr.jp> wrote:
> I use ``trayer'' as systray.
> trayer is a lightweight GTK2-based systray for UNIX desktop.
> # http://fvwm-crystal.org/screenshots.html
> # http://developer.berlios.de/project/showfiles.php?group_id=1595
>
> uim-toolbar-gtk-systray puts icon into trayer.
> When trayer quits, uim-toolbar-gtk-systray crashes.
> gaim also puts, does not crash.
[...]
> (uim-toolbar-gtk-systray:14829): Gdk-WARNING **: GdkWindow 0x1600026 unexpectedly destroyed
>
> (uim-toolbar-gtk-systray:14829): Gdk-WARNING **: GdkWindow 0x1600025 unexpectedly destroyed
>
> (uim-toolbar-gtk-systray:14829): Gdk-WARNING **: GdkWindow 0x1600024 unexpectedly destroyed
>
> (uim-toolbar-gtk-systray:14829): Gdk-WARNING **: GdkWindow 0x1600023 unexpectedly destroyed
>
> (uim-toolbar-gtk-systray:14829): Gdk-WARNING **: GdkWindow 0x1600022 unexpectedly destroyed
>
> (uim-toolbar-gtk-systray:14829): Gdk-WARNING **: GdkWindow 0x1600003 unexpectedly destroyed
> The program 'uim-toolbar-gtk-systray' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadWindow (invalid Window parameter)'.
>   (Details: serial 307 error_code 3 request_code 18 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.)

It may not be a crash but just an unexpected exit of the program by
quitting of systray.  Anyway I added a signal handling for
uim-toolbar-gtk-systray in r4329.  Thanks for your report.

Cheers,
-- 
Etsushi Kato
ek.kato at gmail.com