update-manager crashed with AttributeError in update(): 'NoneType' object has no attribute 'saveDistUpgrade'

Bug #1119427 reported by Uwe Schaibl on 2013-02-08
This bug affects 23 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)

Bug Description

Error Tracker Problem Page:


dialog for steam update crashed?

ProblemType: CrashDistroRelease: Ubuntu 13.04
Package: update-manager 1:0.181
ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6
Uname: Linux 3.8.0-4-generic i686
ApportVersion: 2.8-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Fri Feb 8 15:11:56 2013
ExecutablePath: /usr/bin/update-manager
InstallationDate: Installed on 2012-07-14 (208 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/update-manager
PythonArgs: ['/usr/bin/update-manager']SourcePackage: update-manager
Title: update-manager crashed with AttributeError in update(): 'NoneType' object has no attribute 'saveDistUpgrade'
UpgradeStatus: Upgraded to raring on 2013-01-22 (17 days ago)
UserGroups: adm audio avahi bluetooth cdrom dialout dip lpadmin news plugdev sambashare sudo users vboxusers www-data

Uwe Schaibl (schaibl) wrote :
tags: removed: need-duplicate-check
Changed in update-manager (Ubuntu):
importance: Undecided → Medium
Launchpad Janitor (janitor) wrote :

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

Changed in update-manager (Ubuntu):
status: New → Confirmed
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.

information type: Private → Public
description: updated
Brian Murray (brian-murray) wrote :

From the duplicate bug reports it sound like this error occurs after update-manager has crashed during a previous run.

Weiller (weillerronfini) on 2016-04-03
Changed in update-manager (Ubuntu):
assignee: nobody → Weiller (weillerronfini)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers