Ubuntu

update-manager crashes: AptDaemonError: org.debian.apt: Could not cancel transaction

Reported by Ted Gould on 2010-09-01
700
This bug affects 114 people
Affects Status Importance Assigned to Milestone
Aptdaemon
Undecided
Unassigned
update-manager (Ubuntu)
High
Canonical Foundations Team

Bug Description

Binary package hint: update-manager

Doing and update and canceling it

Then I got an apport dialog.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: update-manager 1:0.142.11
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
NonfreeKernelModules: wl nvidia
Architecture: amd64
Date: Wed Sep 1 09:02:10 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/update-manager
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.6 /usr/bin/update-manager
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/update-manager']
SourcePackage: update-manager
Title: update-manager crashed with AptDaemonError in _convert_dbus_exception()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare tape video

Ted Gould (ted) wrote :
tags: removed: need-duplicate-check
tags: added: bugpattern-needed
Kate Stewart (kate.stewart) wrote :

Based on the number of recent duplicates, this hasn't gone away. Marking it as high.

Possibly this is a duplicate of another bug on update crashing for Natty?

Changed in update-manager (Ubuntu):
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Canonical Foundations Team (canonical-foundations)
Robert Roth (evfool) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

visibility: private → public
Changed in update-manager (Ubuntu):
status: Confirmed → Invalid
status: Invalid → Fix Released

I've marked this bug as fix released, as it's clearly been fixed at some point.

Nest (nestor15) wrote :

Just encountered this bug in Precise!

Brian Murray (brian-murray) wrote :

@Nest - Did you receive an apport crash? If so it would be useful if you were to report it and open a new bug. Thanks in advance.

Nest (nestor15) wrote :

@Brian: When the crach occured the system claimed it was already reported and opened this bug.

I now manually uploaded it as Bug #915413

tom livingston (tlivingston) wrote :

I had this crash occur in precise as well. Note that #915413 was marked as a duplicate of this bug.

Edward Donovan (edward.donovan) wrote :

Apport just sent me here, from an apparent crash, although the update-manager window is still present and functional, after the apport window came up.

I can only offer pretty minor details.

The upgrade was just a day's worth of updates in Precise. It included a new kernel, with update-manager is prompting for restart, in case that's part of the circumstances.

I see the original report (long ago) had proprietary drivers, I can add that this system doesn't have any. Not that anyone may have thought that an issue. :-/

I do these upgrades all the time, and this is the first and only time I've seen this crash. If I figure out anything else about its conditions, or if it happens again, I'll post. Thanks.

More minor points -

The upgrade that was happening seemed to complete fine. No packages were in a half-installed or unconfigured state, and every available update was completed. (And as I said, the update-manager UI didn't go away.)

It looks like gnome-settings daemon was missing, possibly crashed, at the time I saw the apport window. The g-s-d process wasn't running. I realized this when apport started firefox, the UI styling wasn't normal. I don't know if gnome-settings-daemon went down for reasons of its own, and triggered a problem in the update-manager UI. More on that if I think of anything.

Apport did not save the crash report from my system, seeing the bug as a dupe. But since the original report is older, and information was asked for, here is the crash report from my system.

I see that in duplicate bug 915413, apt-daemon crashed just before update-manager. There's no evidence of that in the one time this happened to me. For whatever that's worth...

I should add that I didn't start an upgrade, then cancel it, like the original bug reporter. I ran update-manager, and it was working away when apport came up. These recent reports might be a lot of reasons it's not the same bug, but this is where apport wanted to put it; same errors and stack trace, I guess.

But this bug is marked fixed, and stays that way though apport steers people here. And the title for this bug doesn't seem to fit these later instances.

summary: - Doing and update and canceling it
+ Apport crashes
description: updated
Shahar Or (mightyiam) wrote :

Dear Friends,

I can't read the whole report and comments.

Just to say that this had just occurred to me in precise and that apport had determined that this is this bug.

Thanks and Blessings,
Shahar

tags: added: precise
Kenneth Krak (kennethkrak) wrote :

Update-manager opens a Changelog window, that stops with /tmp/tmp/ and different symbols every time. I usuallly cut it (ctrl-c) and do the update in Synaptic (wich also opens a changelog window, but allows me to close it and do the actual update), today I pressed esc to get rid of the changelog window, and update-manager crashed.
The bug appears every time I use update-manager.

josipogo (josipovic-goran) wrote :

I have the same problem as Kenneth. I am manage to install updates via terminal.
apt-get update
apt-get upgrade -qqyfmb (this procedure never fail)

or Synaptic (also never fail)
Update manager always open Changelog windows and shows the same as Kenneth describe.
System is 12.04, previously was 11.10, 12.04 is update via update-manager.

Cheers.

I cannot reproduce this bug anymore. I doing the way a consumer will
update the OS, from fresh install - updated only thru the update manager
GUI.
On 2012-04-09 8:05 AM, "josipogo" <email address hidden> wrote:

> I have the same problem as Kenneth. I am manage to install updates via
> terminal.
> apt-get update
> apt-get upgrade -qqyfmb (this procedure never fail)
>
> or Synaptic (also never fail)
> Update manager always open Changelog windows and shows the same as Kenneth
> describe.
> System is 12.04, previously was 11.10, 12.04 is update via update-manager.
>
> Cheers.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (643249).
> https://bugs.launchpad.net/bugs/628104
>
> Title:
> Apport crashes
>
> Status in “update-manager” package in Ubuntu:
> Fix Released
>
> Bug description:
> Binary package hint: update-manager
>
> Doing and update and canceling it
>
> Then I got an apport dialog.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 10.10
> Package: update-manager 1:0.142.11
> ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
> Uname: Linux 2.6.35-19-generic x86_64
> NonfreeKernelModules: wl nvidia
> Architecture: amd64
> Date: Wed Sep 1 09:02:10 2010
> EcryptfsInUse: Yes
> ExecutablePath: /usr/bin/update-manager
> InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64
> (20100429)
> InterpreterPath: /usr/bin/python2.6
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python2.6 /usr/bin/update-manager
> ProcEnviron:
> LANG=en_US.utf8
> SHELL=/bin/bash
> PythonArgs: ['/usr/bin/update-manager']
> SourcePackage: update-manager
> Title: update-manager crashed with AptDaemonError in
> _convert_dbus_exception()
> UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd
> lpadmin netdev plugdev sambashare tape video
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/628104/+subscriptions
>

summary: - Apport crashes
+ update-manager crashes
tags: added: not-fixed

This is NOT FIXED, remove the fix release status, just got it in precise

Changed in aptdaemon:
status: New → Confirmed

(Ok, I'm back. It hasn't happened to me again, but I kept thinking about this bug.)

The point in the traceback, that brings everyone to this bug report, is in aptdaemon/errors.py. aptdaemon isn't attached to this bug report; I'm guessing it should be. I'm marking it confirmed 'cause of these recent reports...and because LP is allowing me to.

Perhaps different kinds of crashes are happening here, but the traceback to the error-reporting function is sorting them all to the same place. Just a speculation, because the traceback and the function look fairly generic.

So the important part is "Could not cancel transaction"?

Bug 855394 was about that. Brian says to open a new bug, if it recurs. Whether it's quite the same bug, certainly people are trying to open new bugs here, and launchpad is not letting them.

I don't know this code at all, but I'll keep thinking when I have time. Thanks.

If we don't give LP the trace, then we can file a new bug report. Do we have to sneak around the system that way? A new bug wouldn't have the confirmation and subscribers that are already here. But maybe that's what's called for; I'll try that later if nothing happens here (and if I'm able to get back to this).

summary: - update-manager crashes
+ update-manager crashes: AptDaemonError: org.debian.apt: Could not cancel
+ transaction
tags: removed: not-fixed
Thibault D (thibdrev) wrote :

Yep, just happened when doing an update on Precise.
(right click on the quicklist > Quit, then got the error message)

Steve Langasek (vorlon) wrote :

Reopening, as it appears apport has been filtering off duplicate bugs on the client side, masking the ongoing impact of this issue.

Changed in update-manager (Ubuntu):
status: Fix Released → Triaged

These reports have stopped coming in, here on LP, and on errors.ubuntu.com, as best as I can see. In April, I was pointing out that there were still new reports; since April, there aren't.

Bug 751725 is the same aptdaemon error, seen via software-center rather than update-manager. Someone wiser could consider whether the bug is aptdaemon's, and if these are dupes. That one has no recent LP activity, but still gets hits on Errors.

I only added aptdaemon as a component of that bug today, so unfortunately, I don't see what version of aptdaemon they're running.

Thanks.

I got this error today.
AptDaemon version 0.43+bzr805-0ubuntu7
Update Manager version 1:0.156.14.11
Apport did tell me that my bug is already known and directed me to bug 855394 which is marked "Fix Released"

tags: added: raring
Shao-Wen, Young (b00507031) wrote :

Apport said the bug was already reported and directed me to bug #1026149 (And then opened another window of updatemanager with ONLY title.) I'm using Lubuntu 13.04(amd64) and my kernel version: 3.8.0-16-generic-3.8.0-16.26. It just sits there at "Applying changes", and if you click Details, it just sits there saying, "Preconfiguring packages ...". Before I upgraded my kernel to 3.8.0-16.26, this bug seems not appered.

2green (zendhetmij) wrote :

Ubuntu 13.04, i386, 3 days worth of updates, hangs at "Preconfiguring packages ...".

Are there any workarounds for this problem?

Dimitri John Ledkov (xnox) wrote :

Open terminal:
$ sudo apt-get update
$ sudo apt-get dist-upgrade

To upgrade. This will also bring in updated update-manager which may have fixed this issue once again.

Barry Drake (b-drake) wrote :

I did exactly that - and had two broken packages reported. I did sudo apt-get -f install to fix them and now the update manager is working OK.

Kevin (wittyman37) wrote :

I had this problem yesterday and today in Ubuntu 13.04. I was able to successfully update using the terminal.

Brian Murray (brian-murray) wrote :

Still seems to be occurring regular for 12.04 users - https://errors.ubuntu.com/problem/c7129010b1b083cafb83bef392cc06042c097882

Changed in update-manager (Ubuntu):
milestone: none → ubuntu-12.04.3
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers