DBUS Flaking Out

It looks like DBUS starts flaking out after a few runs inside of buildbot. No idea what's causing the issue, as the trace doesn't involve my code at all.

ERROR:dbus.proxies:Introspect error on org.laptop.ActivityRegistry:/org/laptop/ActivityRegistry:
dbus.exceptions.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.
DEBUG:dbus.proxies:Executing introspect queue due to error
Traceback (most recent call last):
 File "/usr/share/sugar/shell/view/Shell.py", line 98, in _start_journal_idle
   if registry.get_activity('org.laptop.JournalActivity'):
 File "/usr/lib/python2.5/site-packages/sugar/activity/registry.py", line 114, in get_activity
   info_dict = self._registry.GetActivity(service_name)
 File "/var/lib/python-support/python2.5/dbus/proxies.py", line 68, in __call__
   return self._proxy_method(*args, **keywords)
 File "/var/lib/python-support/python2.5/dbus/proxies.py", line 140, in __call__
   **keywords)
 File "/var/lib/python-support/python2.5/dbus/connection.py", line 607, in call_blocking
   message, timeout)
dbus.exceptions.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.
ERROR:dbus.proxies:Introspect error on org.laptop.Clipboard:/org/laptop/Clipboard: dbus.exceptions.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.
DEBUG:dbus.proxies:Executing introspect queue due to error
ERROR:root:Error getting activities async: 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.