Ubuntu
checkbox package

run crashed with KeyError in runner(): 'duration'

Bug #748978 reported by Barry Drake on 2011-04-03

This bug report is a duplicate of: Bug #729431: run crashed with KeyError in runner(): 'duration' System-Check Ubuntu Hardware Database crashed while Microphone check. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	checkbox (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: checkbox

Was using checkbox system testing and came to the point at which it offered to test the update manager: it unexpectedly crashed while attempting to launch the application.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: checkbox 0.11.2
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Sun Apr 3 11:15:53 2011
ExecutablePath: /usr/share/checkbox/run
InterpreterPath: /usr/bin/python2.7
ProcCmdline: python /usr/share/checkbox/run /usr/share/checkbox/configs/checkbox-gtk.ini
ProcEnviron:
SHELL=/bin/bash
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PythonArgs: ['/usr/share/checkbox/run', '/usr/share/checkbox/configs/checkbox-gtk.ini']
SourcePackage: checkbox
Title: run crashed with KeyError in runner(): 'duration'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Barry Drake (b-drake) wrote on 2011-04-03:

Traceback.txt Edit (476 bytes, text/plain; charset="utf-8")

Revision history for this message

Barry Drake (b-drake) wrote on 2011-04-03:

The same thing happened when I continued to the next window and trued to test Nautilus.

Revision history for this message

Apport retracing service (apport) wrote on 2011-04-04: 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 #729431, 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.