glxinfo crashed while checking 3D acceleration

[ezee_duzit]

I am very new
sorry if I didn't get the bug report attached

I am attempting to update/install NVIDIA accelerated graphics driver (Version 180)

after following instructions from forum to check -- glxinfo | grep rendering
no output returned and window stating glxinfo shut down appeared.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/glxinfo
MediaBuild: Ubuntu 9.04 "Jaunty Jackalope" - Release amd64 (20090420.1)
NonfreeKernelModules: nvidia
Package: mesa-utils 7.4-0ubuntu3
ProcCmdline: glxinfo
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersion: Linux version 2.6.28-11-generic (buildd@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5hostname4) ) #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009
Signal: 11
SourcePackage: mesa
StacktraceTop:
 gettimeofday () from /lib/libc.so.6
 ?? () from /usr/lib/libGL.so.1
 _nv000199gl () from /usr/lib/libGLcore.so.1
 _init () from /usr/lib/libGL.so.1
 ?? () from /lib64/ld-linux-x86-64.so.2
Title: glxinfo crashed with SIGSEGV in gettimeofday()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

SegvAnalysis:
 Segfault happened at: 0x7f5f8709cb38 <gettimeofday+24>: callq *%rax
 PC (0x7f5f8709cb38) ok
 source "*%rax" (0x4f6001adac5fd594) not located in a known VMA region (needed readable region)!
 destination "(%rsp)" (0x7fff8fa0ddd0) ok
SegvReason: reading unknown VMA

[Apport retracing service (apport)]

StacktraceTop:gettimeofday () at ../sysdeps/unix/sysv/linux/x86_64/gettimeofday.S:37
?? () from /usr/lib/libGL.so.1
_nv000199gl () from /usr/lib/libGLcore.so.1
_init () from /usr/lib/libGL.so.1
?? ()

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