Version: 2.18.2

What were you doing when the application crashed?
Changing theme for Beryl, re-logged in to the account.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks_Cairo-Human-In-Blue
Icon Theme: Fedora

Memory status: size: 37826560 vsize: 37826560 resident: 17760256 share: 15228928 rss: 17760256 rss_rlim: 4294967295
CPU usage: start_time: 1183503262 rtime: 43 utime: 35 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208101152 (LWP 3363)]
(no debugging symbols found)
0x00513402 in __kernel_vsyscall ()

+ Trace 145570

----------- .xsession-errors ---------------------

Connecting to daemon [ ###         ]
Connecting to daemon [###          ]
Connecting to daemon [ ###         ]
Connecting to daemon [  ###        ]/usr/share/themes/Clearlooks_Cairo-Human-In-Blue/gtk
/usr/share/themes/Clearlooks_Cairo-Human-In-Blue/gtk-2.0/gtkrc:54: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Human-In-Blue/gtk-2.0/gtkrc:55: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.

Connecting to daemon [   ###       ]
Connecting to daemon [    ###      ]
Connecting to daemon [     ###     ]
Connecting to daemon [      ###    ]
Connecting to daemon [       ###   ]
Connecting to 
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 282 error_code 3 request_code 20 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.)

                                        
Connected to daemon in 16316 milliseconds.
Could not open desklet /home/gescape/.gdesklets/Displays/GoodWeather/GoodWeather.display.
Could not open desklet /home/gescape/.gdesklets/Displays/Calendar/Calendar.display.
--------------------------------------------------