What were you doing when the application crashed?
Nothing specific ... I had just unlocked the screensaver and boom bug-buddy launched ...


Distribution: Fedora release 6.91 (Rawhide)
Gnome Release: 2.18.0 2007-03-20 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-1.2999.fc7 #1 SMP Mon Mar 19 20:20:42 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299902
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 50208768 vsize: 50208768 resident: 8724480 share: 6119424 rss: 8724480 rss_rlim: 4294967295
CPU usage: start_time: 1174541469 rtime: 15 utime: 12 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-power-manager'

(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 -1208191264 (LWP 2349)]
(no debugging symbols found)
0x0034e402 in __kernel_vsyscall ()

+ Trace 121029

----------- .xsession-errors (686 sec old) ---------------------
    _dbus_bindings.UInt32(0))
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 169, in __call__
    reply_message = self._connection.send_message_with_reply_and_block(message, timeout)
dbus.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name edu.duke.linux.yum was not provided by any .service files
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x320003a specified for 0x32377b9 (Authentica).
play stio: Failed reading `-': Input not an Ogg Vorbis audio stream
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 54 error_code 11 request_code 140 minor_code 19)
  (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.)
--------------------------------------------------