Public bug reported:
Whenever I try to run zeitgeist-daemon, I get the following exception
that leads to a crash:
> zeitgeist-daemon --replace
DEBUG:zeitgeist.engine:Creating engine 'querymancer'
INFO:zeitgeist.engine:Creating database:
/home/bkoenig/.local/share/zeitgeist/database.sqlite
DEBUG:root:Checking for another running instance...
DEBUG:root:Replacing currently running process.
ERROR:dbus.proxies:Introspect error on :1.396:/org/gnome/zeitgeist:
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/bin/zeitgeist-daemon", line 43, in <module>
obj = RemoteInterface(mainloop = mainloop)
File "/usr/share/zeitgeist/_zeitgeist/engine/remote.py", line 38, in __init__
SingletonApplication.__init__(self)
File "/usr/share/zeitgeist/_zeitgeist/singleton.py", line 48, in __init__
interface = DBusInterface()
File "/usr/lib/pymodules/python2.6/zeitgeist/dbusutils.py", line 137, in
__init__
proxy = self._get_proxy()
File "/usr/lib/pymodules/python2.6/zeitgeist/dbusutils.py", line 94, in
_get_proxy
introspection_xml = cls.__shared_state["proxy_object"].Introspect()
File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 68, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
**keywords)
File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, 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.
** Affects: zeitgeist
Importance: Undecided
Status: New
--
zeitgeist-daemon crashes with exception
https://bugs.launchpad.net/bugs/496750
You received this bug notification because you are a member of Zeitgeist
Developers, which is the registrant for Zeitgeist Framework.
Status in Zeitgeist Framework: New
Bug description:
Whenever I try to run zeitgeist-daemon, I get the following exception that
leads to a crash:
> zeitgeist-daemon --replace
DEBUG:zeitgeist.engine:Creating engine 'querymancer'
INFO:zeitgeist.engine:Creating database:
/home/bkoenig/.local/share/zeitgeist/database.sqlite
DEBUG:root:Checking for another running instance...
DEBUG:root:Replacing currently running process.
ERROR:dbus.proxies:Introspect error on :1.396:/org/gnome/zeitgeist:
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/bin/zeitgeist-daemon", line 43, in <module>
obj = RemoteInterface(mainloop = mainloop)
File "/usr/share/zeitgeist/_zeitgeist/engine/remote.py", line 38, in __init__
SingletonApplication.__init__(self)
File "/usr/share/zeitgeist/_zeitgeist/singleton.py", line 48, in __init__
interface = DBusInterface()
File "/usr/lib/pymodules/python2.6/zeitgeist/dbusutils.py", line 137, in
__init__
proxy = self._get_proxy()
File "/usr/lib/pymodules/python2.6/zeitgeist/dbusutils.py", line 94, in
_get_proxy
introspection_xml = cls.__shared_state["proxy_object"].Introspect()
File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 68, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
**keywords)
File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, 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.
_______________________________________________
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
