nvidia-xconfig crashed with ImportError in <module> from XKit import xutils, xorgparaser ImoportError: No module named XKit

[Nerdopolis]

I am using the latest Ubuntu as of 3/9/09. (Jaunty with updates) I tried to run nvidia-xconfig, and I recived this error.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nvidia-xconfig
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: nvidia-glx-173 173.14.16-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/bin/nvidia-xconfig
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-8-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu1) ) #28-Ubuntu SMP Thu Mar 5 21:49:36 UTC 2009
PythonArgs: ['/usr/bin/nvidia-xconfig']
SourcePackage: nvidia-graphics-drivers-173
Title: nvidia-xconfig crashed with ImportError in <module>()
Traceback:
 Traceback (most recent call last):
   File "/usr/bin/nvidia-xconfig", line 4, in <module>
     from XKit import xutils, xorgparser
 ImportError: No module named XKit
Uname: Linux 2.6.28-8-generic i686
UserGroups:

glxinfo:

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface [8086:2560] (rev 01)
     Subsystem: Dell Device [1028:0126]
01:00.0 VGA compatible controller [0300]: nVidia Corporation NV36GL [Quadro FX 1100] [10de:034e] (rev a1)
     Subsystem: nVidia Corporation Device [10de:01da]
  Status: Dev=00:00.0 64bit- 133MHz- SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz-

[bugbot (bugbot)]

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.