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

[Nicolas DERIVE]

Starting Ubuntu natty desktop session (with unity) I got this bug.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nux-tools 0.9.18-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
Uname: Linux 2.6.38-1-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed Feb 2 13:48:24 2011
ExecutablePath: /usr/lib/nux/unity_support_test
ProcCmdline: /usr/lib/nux/unity_support_test
ProcEnviron:
 LANGUAGE=fr_FR.UTF-8:fr:en_GB:en
 LANG=fr_FR.UTF-8
 LC_MESSAGES=fr_BE.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xe56257 <_ZNK3nux9GpuDevice21GetOpenGLMajorVersionEv+7>: mov 0x50(%eax),%eax
 PC (0x00e56257) ok
 source "0x50(%eax)" (0x00000050) 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 cdrom dialout dip fax floppy fuse plugdev tape video
XsessionErrors:
 (nautilus:1673): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (<unknown>:1679): Gtk-CRITICAL **: IA__gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed
 (unity-2d-launcher:1678): Gtk-CRITICAL **: IA__gtk_icon_info_load_icon: assertion `icon_info != NULL' failed
 (unity-2d-launcher:1678): Gtk-CRITICAL **: IA__gtk_icon_info_load_icon: assertion `icon_info != NULL' 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.