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

[Yo]

Binary package hint: gnome-screensaver

activate driver privative in HP pavilion dv4-14123la , AMD athlon X2 64 Bits

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-screensaver 2.30.2-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: fglrx wl
Architecture: i386
Date: Sat Apr 9 14:48:13 2011
ExecutablePath: /usr/lib/gnome-screensaver/gnome-screensaver-gl-helper
GconfGnomeSession:
 idle_delay = 5
  /desktop/gnome/session/required_components:
   windowmanager = gnome-wm
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
ProcCmdline: /usr/lib/gnome-screensaver/gnome-screensaver-gl-helper
ProcEnviron:
 LANGUAGE=es_CO:en
 PATH=(custom, no user)
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x680824 <XF86DRIQueryExtension+142>: movzbl 0x4(%esi),%edx
 PC (0x00680824) 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 0x00680824 in XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
 No symbol table info available.
 #1 0x00b54ae6 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-09 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WindowManager: gnome-wm

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