Comment 7 for bug 722762

Please reactivate this bug because it occurs on my PC (Thinkpad T60) too.

Ubuntu Release: 11.04 (64bit)
Zeitgeist Version: 0.7.1-1

This bug is reproducible.

Happens after (re)starting Ubuntu. Replacing Zeitgeist daemon does not work for me (can't connect to running process. Gone rogue?):
$ zeitgeist-daemon --replace
[2011-07-22 11:18:41,908] - DEBUG - singleton - Checking for another running instance...
[2011-07-22 11:18:41,912] - DEBUG - root - Replacing currently running process...
[2011-07-22 11:19:06,937] - ERROR - dbus.proxies - Introspect error on :1.251:/org/gnome/zeitgeist/log/activity: 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.
[2011-07-22 11:19:06,938] - DEBUG - dbus.proxies - Executing introspect queue due to error
Traceback (most recent call last):
  File "/usr/bin/zeitgeist-daemon", line 162, in <module>
    mainloop, interface = setup_interface()
  File "/usr/bin/zeitgeist-daemon", line 102, in setup_interface
    return mainloop, RemoteInterface(mainloop = mainloop)
  File "/usr/share/zeitgeist/_zeitgeist/engine/remote.py", line 69, in __init__
    SingletonApplication.__init__(self)
  File "/usr/share/zeitgeist/_zeitgeist/singleton.py", line 54, in __init__
    self._handle_existing_instance()
  File "/usr/share/zeitgeist/_zeitgeist/singleton.py", line 87, in _handle_existing_instance
    interface = ZeitgeistDBusInterface()
  File "/usr/lib/pymodules/python2.7/zeitgeist/client.py", line 235, in __init__
    self.INTERFACE_NAME, self.OBJECT_PATH)
  File "/usr/lib/pymodules/python2.7/zeitgeist/client.py", line 149, in __init__
    self.__methods, self.__signals = self.get_members(proxy.Introspect())
  File "/usr/lib/pymodules/python2.7/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/pymodules/python2.7/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/pymodules/python2.7/dbus/connection.py", line 630, 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.