apturl crashes with KeyError in __getitem__() if package does not exist

Bug #124943 reported by Toby Smithe
12
Affects Status Importance Assigned to Milestone
apturl (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: apturl

If the specified package does not exist, apturl will crash as reported by apport in this ticket.

ProblemType: Crash
Architecture: i386
Date: Mon Jul 9 21:50:21 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/apturl
InterpreterPath: /usr/bin/python2.5
Package: apturl 0.0+bzr20070709
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/apturl apt:blah
ProcCwd: /home/toby
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/toby/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
PythonArgs: ['/usr/bin/apturl', 'apt:blah']
SourcePackage: apturl
Title: apturl crashed with KeyError in __getitem__()
Uname: Linux leopard 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

Tags: apport-crash
Revision history for this message
Toby Smithe (tsmithe) wrote :
Revision history for this message
Toby Smithe (tsmithe) wrote : Re: [Bug 124943] apturl crashes with KeyError in __getitem__() if package does not exist

On Mon, 2007-07-09 at 20:50 +0000, Toby Smithe wrote:
> *** This bug is a duplicate of bug 124942 ***
> https://bugs.launchpad.net/bugs/124942

Now, if bug 124942 was public, I wouldn't have spammed the bugmail with
my duplicate. Why is it private? Does this happen with a lot of reports?
Since I am now a subscriber through my dupe, why can I still not access
it from the web interface?

Revision history for this message
Adrien Cunin (adri2000) wrote :
Revision history for this message
Toby Smithe (tsmithe) wrote : Re: [Bug 124943] Re: apturl crashes with KeyError in __getitem__() if package does not exist

On Tue, 2007-07-10 at 00:27 +0000, Adrien Cunin wrote:
> Toby: see https://lists.ubuntu.com/archives/ubuntu-devel-announce/2007-July/000312.html
> I've now made #124942 public.

Ahh, thank you; I had completely forgotten that. This bug was private
initially, but I thought it must have been an error on my part
somewhere.

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.