Ubuntu
update-manager package

update-manager crashed with AptDaemonError in _convert_dbus_exception()

Bug #635443 reported by Muriel de Souza Godoi on 2010-09-11

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

Asus 1008ha model

Description: Ubuntu maverick (development branch)
Release: 10.10

update-manager:
  Instalado: 1:0.142.13
  Candidato: 1:0.142.13
  Tabela de versão:
*** 1:0.142.13 0
        500 http://br.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: update-manager 1:0.142.13
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic i686
Architecture: i386
Date: Fri Sep 10 18:18:47 2010
ExecutablePath: /usr/bin/update-manager
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.6 /usr/bin/update-manager
ProcEnviron:
LANGUAGE=pt_BR:pt:en
LANG=pt_BR.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/update-manager']
SourcePackage: update-manager
Title: update-manager crashed with AptDaemonError in _convert_dbus_exception()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Muriel de Souza Godoi (murielgodoi) wrote on 2010-09-11:

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

Revision history for this message

Apport retracing service (apport) wrote on 2010-09-13: 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.