jockey-gtk crashed with OSError in _execute_child()

[steveacab]

Lucid
jockey-gtk version 0.5.6-0ubuntu2

ProblemType: Crash
Architecture: i386
Date: Thu Feb 11 05:19:08 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
InterpreterPath: /usr/bin/python2.6
MachineType: System Manufacturer System Name
NonfreeKernelModules: nvidia
Package: jockey-gtk 0.5.6-0ubuntu2
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-10-generic root=UUID=4f2b812f-2de2-4e30-ac2f-c091494ae231 ro quiet splash
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
 LANG=it_IT.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
PythonArgs: ['/usr/bin/jockey-gtk']
SourcePackage: jockey
Title: jockey-gtk crashed with OSError in _execute_child()
Uname: Linux 2.6.32-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 06/08/2004
dmi.bios.vendor: Award Software, Inc.
dmi.bios.version: ASUS P4S800 ACPI BIOS Revision 1009
dmi.board.name: P4S800
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: REV 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 7
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP4S800ACPIBIOSRevision1009:bd06/08/2004:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4S800:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion:
dmi.product.name: System Name
dmi.product.version: System Version
dmi.sys.vendor: System Manufacturer

[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 #518879, 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.