update-manager crashed with KeyError in __getitem__()

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

Bug Description

Binary package hint: update-manager

update-manager doesn't seem to like it very much when I have apt configured for multiarch. This crash appears to happen because a binary package, ecj1, exists for armel but not for the native arch (amd64).

To reproduce:

echo 'deb [arch=armel] http://ports.ubuntu.com/ubuntu-ports/ maverick main restricted' >> /etc/apt/sources.list
echo 'APT::Architectures { "amd64"; "armel"; };' > /etc/apt/apt.conf.d/multiarch-me
apt-get update
update-manager

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: update-manager 1:0.142.22
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic x86_64
Architecture: amd64
Date: Mon Feb 7 23:25:01 2011
ExecutablePath: /usr/bin/update-manager
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.6 /usr/bin/update-manager
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.utf8
PythonArgs: ['/usr/bin/update-manager']
SourcePackage: update-manager
Title: update-manager crashed with KeyError in __getitem__()
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare src

Revision history for this message
Steve Langasek (vorlon) wrote :
tags: added: multiarch
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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #444306, 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
Revision history for this message
Steve Langasek (vorlon) wrote :

same backtrace, different cause. un-duping.

Revision history for this message
RedSingularity (redsingularity) wrote :

Marking as a duplicate of bug 742101. Even though this was reported first, bug 742101 has a better description. Linking to that one.

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.