update-manager crashed with KeyError in __getitem__(): "The cache has no package named 'linux-headers-3.2.0-14-generic'"

Bug #931693 reported by Oleg
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

update

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: update-manager 1:0.156.3
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CurrentDmesg.txt:
 [ 46.398668] init: plymouth-stop pre-start process (1408) terminated with status 1
 [ 52.888028] eth2: no IPv6 routers present
Date: Tue Feb 14 01:02:46 2012
DpkgHistoryLog.txt:

DpkgTerminalLog.txt:

DuplicateOf: https://bugs.launchpad.net/bugs/927274
ExecutablePath: /usr/bin/update-manager
GsettingsChanges:
 com.ubuntu.update-manager first-run false
 com.ubuntu.update-manager launch-time 1329166711
 com.ubuntu.update-manager window-height 500
 com.ubuntu.update-manager window-width 600
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/update-manager --no-focus-on-map
PythonArgs: ['/usr/bin/update-manager', '--no-focus-on-map']
SourcePackage: update-manager
Title: update-manager crashed with KeyError in __getitem__(): "The cache has no package named 'linux-headers-3.2.0-14-generic'"
UpgradeStatus: Upgraded to precise on 2012-02-13 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Oleg (msodmin) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #927274, 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.

tags: removed: need-duplicate-check
visibility: private → public
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.