jockey-gtk crashed with OSError in _execute_child()

[thoshiro1]

driver video dont install,and some upgrade also.
driver video non si installa.Durante aggiornamento alcuni pacchetti non vengono aggiornati.

ProblemType: Crash
Architecture: amd64
Date: Fri Feb 12 14:16:49 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100131)
InterpreterPath: /usr/bin/python2.6
Lsusb:
 Bus 002 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 003: ID 090c:1000 Feiya Technology Corp. Flash Drive
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
NonfreeKernelModules: nvidia
Package: jockey-gtk 0.5.7-0ubuntu1
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-12-generic root=UUID=72bc0333-46ba-4d88-b2fc-82845fc88c9a ro quiet splash
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
 LANG=it_IT.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-12.17-generic
PythonArgs: ['/usr/bin/jockey-gtk']
SourcePackage: jockey
Title: jockey-gtk crashed with OSError in _execute_child()
Uname: Linux 2.6.32-12-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 10/22/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6
dmi.board.name: NF-CK804
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: GA K8NXP-SLI
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd10/22/2008:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnNF-CK804:rvrGAK8NXP-SLI:cvn:ct3:cvr:

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