What were you doing when the application crashed?
nothing ... the machine was just minding its own buisness


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.22.2 2008-06-03 (Ubuntu)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: Human

Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0



----------- .xsession-errors (13871 sec old) ---------------------
Throttle level is 5
evolution-alarm-notify-Message: Setting timeout for 55255 1215640800 1215585545
evolution-alarm-notify-Message:  Thu Jul 10 00:00:00 2008
evolution-alarm-notify-Message:  Wed Jul  9 08:39:05 2008
seahorse nautilus module initialized
Initializing nautilus-share extension
** (nautilus:6115): WARNING **: Unable to add monitor: Not supported
blinklight-fixperm: Could not stat procfile /proc/acpi/asus/mled: No such file or directory
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400060 (Buddy List)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
  PID TTY          TIME CMD
 6091 ?        00:00:00 pulseaudio
--------------------------------------------------
Gimmie Version: 0.2.8

Traceback (most recent call last):

+ Trace 202388