jockey-gtk crashed with OSError in _execute_child()

[Nizar Kerkeni]

jockey crashed when trying to activate nvidia current proprietary driver.

ProblemType: Crash
Architecture: amd64
Date: Tue Feb 9 20:07:48 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
MachineType: Sony Corporation VGN-FE31H
NonfreeKernelModules: nvidia
Package: jockey-gtk 0.5.6-0ubuntu2
PackageArchitecture: all
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-12-generic root=UUID=76538051-9b55-476d-a8ad-e0f46ab3bf4c ro quiet splash
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
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 audio cdrom dialout dip fax lpadmin netdev plugdev sambashare tape vboxusers video
dmi.bios.date: 08/17/2006
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R0170J3
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: 7R2M000000003d0b2f3d48aa3a3f
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: C3LMPW7F
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0170J3:bd08/17/2006:svnSonyCorporation:pnVGN-FE31H:pvrC3LMPW7F:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrC3LMPW7F:
dmi.product.name: VGN-FE31H
dmi.product.version: C3LMPW7F
dmi.sys.vendor: Sony Corporation

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