bughugger crashed with ValueError in <lambda>()

[C de-Avillez]

Binary package hint: bughugger

Release of Ubuntu:
Package Version:
Expected Results:
Actual Results:

ProblemType: Crash
Architecture: amd64
Date: Wed Feb 17 14:31:39 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/bughugger
InterpreterPath: /usr/bin/python2.6
Package: bughugger 10.02.1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/bughugger
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.utf8
 LC_TIME=en_DK.utf8
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
PythonArgs: ['/usr/bin/bughugger']
SourcePackage: bughugger
Title: bughugger crashed with ValueError in <lambda>()
Uname: Linux 2.6.32-13-generic x86_64
UserGroups: adm admin audio cdrom dialout fuse kvm libvirtd lpadmin netdev plugdev sambashare vboxusers

[C de-Avillez (hggdh2)]

fun... bughugger kept on retrying, and crashing, and triggering apport again and again ;-). A 'killall bughugger' dealt with it.

[C de-Avillez (hggdh2)]

Easily reproducible: prepare a filter as Importance > High. Bang, followed by a loop. If apport trapping is enabled, multiple apport-gtk will be started.

Of course, Importance > High is invalid.

[C de-Avillez (hggdh2)]

Another way to reproduce: filter on (say) package contains whatever.

THEN change to

 - status
 - any relation
BANG!

since bughugger starts processing the new filter as soon as you start typing, you do not have time to change the value field.

[papukaija (papukaija)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, this bug report is being closed due to the unmaintained status of bughugger. Please see bug 852179 for more information. Thanks.