Ubuntu
update-manager package

update-manager crashed with AptDaemonError in _convert_dbus_exception(): org.debian.apt: Could not cancel transaction

Bug #770010 reported by njsf on 2011-04-24

This bug report is a duplicate of: Bug #628104: update-manager crashes: AptDaemonError: org.debian.apt: Could not cancel transaction. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	update-manager (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: update-manager

Doing regular update

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: update-manager 1:0.147.6
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Sun Apr 24 16:21:25 2011
ExecutablePath: /usr/bin/update-manager
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.7 /usr/bin/update-manager
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/update-manager']
SourcePackage: update-manager
Title: update-manager crashed with AptDaemonError in _convert_dbus_exception(): org.debian.apt: Could not cancel transaction
UpgradeStatus: Upgraded to natty on 2011-04-15 (9 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

njsf (nelson-ferreira) wrote on 2011-04-24:

Traceback.txt Edit (465 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-06-07: 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 #628104, 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.