Comment 41 for bug 616721

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Got this crash on Precise by clicking on 'Check' in update-manager.

This is the error message I get from apt-daemon

18:42:39 AptDaemon [INFO]: Initializing daemon
18:42:39 AptDaemon [WARNING]: Replacing already running daemon
ERROR:dbus.proxies:Introspect error on :1.163:/org/debian/apt: 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.
Traceback (most recent call last):
  File "/usr/sbin/aptd", line 28, in <module>
    aptdaemon.core.main()
  File "/usr/lib/python2.7/dist-packages/aptdaemon/core.py", line 2157, in main
    daemon = AptDaemon(options, bus=bus)
  File "/usr/lib/python2.7/dist-packages/aptdaemon/core.py", line 1350, in __init__
    timeout=300)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 143, in __call__
    **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)