unity_support_test crashed with SIGSEGV in XF86DRIQueryExtension()

[Hee-Young Shin]

unity support test abruptly stopped functioning in a new booting

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nux-tools 0.9.38-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
CrashCounter: 1
Date: Sun Apr 3 17:58:11 2011
DistroCodename: natty
DistroVariant: ubuntu
ExecutablePath: /usr/lib/nux/unity_support_test
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InstallationMedia_: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: /usr/lib/nux/unity_support_test
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature_: Ubuntu 2.6.38-7.39-generic 2.6.38
SegvAnalysis:
 Segfault happened at: 0x189824 <XF86DRIQueryExtension+142>: movzbl 0x4(%esi),%edx
 PC (0x00189824) ok
 source "0x4(%esi)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
Stacktrace:
 #0 0x00189824 in XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
 No symbol table info available.
 #1 0x0075faa6 in ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
 No symbol table info available.
StacktraceTop:
 XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: unity_support_test crashed with SIGSEGV in XF86DRIQueryExtension()
UpgradeStatus: Upgraded to natty on 2011-04-01 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu1

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