What were you doing when the application crashed?
startup


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.18.1 2007-04-10 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gentle
Icon Theme: nuoveXT-1.6

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 (13 sec old) ---------------------
** (trackerd:5335): WARNING **: Tracker daemon is already running - exiting
inotify_add_watch: No such file or directory
Made widgetMade widgetTraceback (most recent call last):

+ Trace 130383

Initializing gnome-mount extension
** Message: failed to load session from /home/lucas/.nautilus/saved-session-SW48QT
--------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/deskbar/ModuleLoader.py", line 157, in load_all
    self.load (f)
  File "/usr/lib/python2.5/site-packages/deskbar/ModuleLoader.py", line 139, in load
    mod_instance = getattr (mod, handler) ()
  File "/usr/lib/deskbar-applet/handlers/tracker-handler.py", line 201, in __init__
    self.tracker = bus.get_object('org.freedesktop.Tracker','/org/freedesktop/tracker')
  File "/var/lib/python-support/python2.5/dbus/_dbus.py", line 410, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 230, in __init__
    _dbus_bindings.UInt32(0))
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 169, in __call__
    reply_message = self._connection.send_message_with_reply_and_block(message, timeout)
DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.