aptd crashed with LookupError in remove_from_connection()

Bug #437091 reported by Dave H
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
aptdaemon (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: aptdaemon

Not sure what this relates to. I had just rebooted after an update attempt, saw the crash icon in the system try.
 I was logged on as me and started Update manager, clicked on check, it asked for a password, I entered my password and the enter dialog window just stayed there with the hour glass. Cant remember how it exited but no update occurred I think? There was network, cpu and HD activity.

I think this is caused by update manager not being able to coupe with incorrect password entry. I'm a bit sloppy on the keyboard.

Hardware: Lenovo S10e netbook.

Karmic Alpha 6 base + updates.

ProblemType: Crash
Architecture: i386
Date: Sat Sep 26 09:08:23 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/aptd
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: wl
Package: aptdaemon 0.10+bzr240-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/aptd
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.31-11.36-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/a603aa5713a14d10bbcf048f4c2de217 at 0x94d574c> is not exported at a location matching (None,None)
Uname: Linux 2.6.31-11-generic i686
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.