backend crashed with ValueError in loads()

[Darin Miller]

Binary package hint: checkbox

1st issue, server could not be found, followed by:
Failed to process form: 'field.submission_data' is not a valid key as per {'field.architecture': <functools.partial object at 0x2751e10>, 'field.distribution': <functools.partial object at 0x2771520>, 'field.system': <functools.partial object at 0x2771578>, 'field.actions.upload': <functools.partial object at 0x27715d0>, 'field.private': <functools.partial object at 0x2771628>, 'field.format': <functools.partial object at 0x2771680>, 'field.contactable': <functools.partial object at 0x27716d8>, 'field.date_created': <functools.partial object at 0x2771730>, 'field.emailaddress': <functools.partial object at 0x2771788>, 'field.submission_key': <functools.partial object at 0x27717e0>, 'field.distroseries': <functools.partial object at 0x2771838>, 'field.live_cd': <functools.partial object at 0x2771890>}

Then the crashed occurred.

ProblemType: Crash
Architecture: amd64
Date: Sun Mar 21 11:16:38 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/share/checkbox/backend
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: checkbox 0.9
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/checkbox/backend /tmp/checkboxHNHijr/input /tmp/checkboxHNHijr/output
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.utf8
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
PythonArgs: ['/usr/share/checkbox/backend', '/tmp/checkboxHNHijr/input', '/tmp/checkboxHNHijr/output']
SourcePackage: checkbox
Title: backend crashed with ValueError in loads()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups:

[Apport retracing service (apport)]

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 #536645, 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.