gnome-screensaver-gl-helper crashed with SIGSEGV in XF86DRIQueryExtension()

[joshiss]

Binary package hint: gnome-screensaver

using hp probook 4420s

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-screensaver 2.30.2-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
Architecture: i386
Date: Tue Apr 12 13:35:50 2011
ExecutablePath: /usr/lib/gnome-screensaver/gnome-screensaver-gl-helper
GconfGnomeSession:
 idle_delay = 5
  /desktop/gnome/session/required_components:
   windowmanager = metacity
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/lib/gnome-screensaver/gnome-screensaver-gl-helper
ProcCwd: /
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, user)
 LANG=en_IN
 LC_MESSAGES=en_IN.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb70de824 <XF86DRIQueryExtension+142>: movzbl 0x4(%esi),%edx
 PC (0xb70de824) 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: gnome-screensaver
Stacktrace:
 #0 0xb70de824 in XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
 No symbol table info available.
 #1 0xb7716ae6 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: gnome-screensaver-gl-helper crashed with SIGSEGV in XF86DRIQueryExtension()
UpgradeStatus: Upgraded to natty on 2011-04-12 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WindowManager: metacity
XsessionErrors: (nautilus:2039): GConf-CRITICAL **: gconf_value_free: assertion `value != 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 #750010, 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.