aptd crashed with LookupError in remove_from_connection()

Bug #436318 reported by Paul Hummer
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
aptdaemon (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: aptdaemon

After an `apt-get upgrade` I rebooted my system and logged in. I immediately saw this crash notification. I'm assuming that apport is doing all the heavy lifting, because I don't have any details other than that.

aptdaemon:
  Installed: 0.10+bzr240-0ubuntu1
  Candidate: 0.10+bzr240-0ubuntu1
  Version table:
 *** 0.10+bzr240-0ubuntu1 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
Date: Wed Sep 23 16:41:36 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/aptd
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha amd64 (20090714)
Package: aptdaemon 0.10+bzr240-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/aptd
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
PythonArgs: ['/usr/sbin/aptd']
SourcePackage: aptdaemon
Title: aptd crashed with LookupError in remove_from_connection()
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/pymodules/python2.6/dbus/service.py", line 621, in remove_from_connection
     '(%r,%r)' % (self, connection, path))
 LookupError: <aptdaemon.core.Transaction at /org/debian/apt/transaction/836564a230df466a89f55d2491532808 at 0x190bd50> is not exported at a location matching (None,None)
Uname: Linux 2.6.31-10-generic x86_64
UserGroups:

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #422585, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.