unity_support_test crashed with SIGSEGV in nux::GpuDevice::GetOpenGLMajorVersion()

[Id2ndR]

I install nvidia-current using jockey but jockey didn't do the job correctly (no /etc/X11/xorg.conf).

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nux-tools 0.9.18-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-2.29-generic 2.6.38-rc3
Uname: Linux 2.6.38-2-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CheckboxSubmission: 1085bd3e1d3dc5fdefc443fc7f3687c2
CheckboxSystem: f78c696d4c0399fa91f9da1b540d7fd0
CrashCounter: 1
Date: Tue Feb 8 19:32:55 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/nux/unity_support_test
ProcCmdline: /usr/lib/nux/unity_support_test
ProcEnviron:
 LANGUAGE=fr_FR:fr:en_GB:en
 LANG=fr_FR.UTF-8
 LC_MESSAGES=fr_FR.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fe9c485a640 <_ZNK3nux9GpuDevice21GetOpenGLMajorVersionEv>: mov 0x88(%rdi),%eax
 PC (0x7fe9c485a640) ok
 source "0x88(%rdi)" (0x00000088) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 nux::GpuDevice::GetOpenGLMajorVersion() const () from /usr/lib/libnux-graphics-0.9.so.0
 ?? ()
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
Title: unity_support_test crashed with SIGSEGV in nux::GpuDevice::GetOpenGLMajorVersion()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (nautilus:2892): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (nm-applet:2909): Gtk-CRITICAL **: IA__gtk_widget_is_toplevel: assertion `GTK_IS_WIDGET (widget)' failed
 (nm-applet:2909): Gtk-CRITICAL **: IA__gtk_widget_is_toplevel: assertion `GTK_IS_WIDGET (widget)' failed
 (nm-applet:2909): Gtk-CRITICAL **: IA__gtk_widget_is_toplevel: assertion `GTK_IS_WIDGET (widget)' failed

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