Ubuntu
update-manager package

update-manager crashed with DBusException in commit()

Bug #651408 reported by vlotho on 2010-09-29

This bug report is a duplicate of: Bug #618951: update-manager crashed with DBusException in commit(). 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

gilles@ubuntu1010:~$ lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10
gilles@ubuntu1010:~$ apt-cache policy update-manager
update-manager:
  Installé : 1:0.142.15
  Candidat : 1:0.142.15
Table de version :
*** 1:0.142.15 0
        500 http://fr.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: update-manager 1:0.142.15
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Wed Sep 29 21:10:33 2010
ExecutablePath: /usr/bin/update-manager
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100831.2)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.6 /usr/bin/update-manager
ProcEnviron:
PATH=(custom, user)
LANG=fr_FR.utf8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/update-manager']
SourcePackage: update-manager
Title: update-manager crashed with DBusException in commit()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

vlotho (gdalmas) wrote on 2010-09-29:

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

Revision history for this message

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