backend crashed with ValueError in loads()

[Ken Weill P. Lumacad]

Binary package hint: checkbox

I was trying to run System Testing from System - Administration.
Then it crashed, i can't remember the crash message. Then apport comes out with "Collecting Problem Information", then a few seconds, 2nd crash occurs, which makes to apport dialog box running.

The 2nd crash produced this report.
The 1st crash, is still running with "Collecting Problem Information", as of this writing. So, i have no other choice but to cancel the 1st apport dialog box as its been running for more than 5 minutes.

Don't have any idea what's the cause of this problem.

ProblemType: Crash
Architecture: i386
Date: Thu Mar 11 23:23:02 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/share/checkbox/backend
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
InterpreterPath: /usr/bin/python2.6
Package: checkbox 0.9
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/checkbox/backend /tmp/checkboxtcjJTr/input /tmp/checkboxtcjJTr/output
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_PH.utf8
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
PythonArgs: ['/usr/share/checkbox/backend', '/tmp/checkboxtcjJTr/input', '/tmp/checkboxtcjJTr/output']
SourcePackage: checkbox
Title: backend crashed with ValueError in loads()
Uname: Linux 2.6.32-16-generic i686
UserGroups:

[Ken Weill P. Lumacad (cyberlazi)]

i tried to run System Testing again and it crashed again, with another error.
Crashed reported here:
https://bugs.launchpad.net/ubuntu/+source/checkbox/+bug/537435

[Ken Weill P. Lumacad (cyberlazi)]

hmmm... i tried to run Users and Groups from System - Administration, then it crashed again.

backend crashed with ValueError in loads()

i think it will be duplicated to select report a new bug, so, i will file a new report.

[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.