check_gl_texture_size crashed with SIGSEGV in __libc_start_main()

[Eyad Salah]

On Startup

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libgnome-desktop-3-2 3.2.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CheckboxSubmission: 6a005c47a693737f8a587c2893ed61f5
CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
CrashCounter: 1
Date: Thu Oct 6 09:36:17 2011
ExecutablePath: /usr/lib/gnome-desktop3/check_gl_texture_size
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/gnome-desktop3/check_gl_texture_size
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x400872: mov 0xe0(%rax),%esi
 PC (0x00400872) ok
 source "0xe0(%rax)" (0x000000e0) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-desktop3
StacktraceTop:
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
 ?? ()
Title: check_gl_texture_size crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: Upgraded to oneiric on 2011-09-27 (8 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
XsessionErrors:
 (bluetooth-applet:2178): Bluetooth-WARNING **: Could not open RFKILL control device, please verify your installation
 (nautilus:2169): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
 (nautilus:2169): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
 (gwibber-service:2482): libindicate-WARNING **: Menu being changed when the indicator is visible. Listeners will NOT be notified of this change.

[Apport retracing service (apport)]

StacktraceTop: main (argc=<optimized out>, argv=<optimized out>) at check_gl_texture_size.c:39

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #862161, so it 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. Feel free to continue to report any other bugs you may find.