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

[ChrischanM]

installation of 11.10 beta 1 alongside 10.04 (no upgrade)
update manager crashed while "applying changes", but continued later

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: update-manager 1:0.152.18
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Wed Sep 21 11:29:57 2011
ExecutablePath: /usr/bin/update-manager
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/update-manager
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
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: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

This crash has the same stack trace characteristics as bug #628104. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jean-Baptiste Lallement (jibel)]

marking as high as it seems to be a regression (628104 is fixed)

[Michael Vogt (mvo)]

This happens inside the aptdaemon gtkwidgets, I reassign.

[Brian Murray (brian-murray)]

There really was no clear indication, a changelog for example, that bug 628104 was really fixed.

In at least bug 915413 the reporter mentions aptdaemon crashing on them, which would explain clicking Cancel failing.

I've tried recreating this in Precise by just canceling the installation of updates and have not been successful.

[Brian Murray (brian-murray)]

As we have not received any duplicates of this bug since January and the bug pattern has received no hits, I am going to mark this bug report as Fix Released for Precise and set the Oneiric task to Won't Fix. In the event that anyone encounters this bug in the future please report a new crash report.

[Edward Donovan (edward.donovan)]

I think Brian may be right that bug 628104 is not really fixed. It's possible this pattern hasn't appeared, because it now hits that bug, which is assigned to update-manager, and marked fixed. People are trying to open new bugs on a crash, but keep getting duped to a bug they can't change the status of. These look related, if not the same. Thanks.

[Edward Donovan (edward.donovan)]

Oh, I forgot to add -- I don't see that anyone can reproduce it on demand. As you said, I can't reproduce it by just cancelling. Stumped for the moment, sorry.

[Edward Donovan (edward.donovan)]

Of course, in the one time it happened to me, I didn't even cancel the transaction, IIRC. It happened during an upgrade, unprompted as far as I could see.

[Edward Donovan (edward.donovan)]

Excuse my run-on commenting, as I keep thinking. Two users there, as of a week ago, were reproducing it. They did not subscribe to the bug, unfortunately...do we just email them?

[Edward Donovan (edward.donovan)]

I've tried filing a new report: bug 982767.