[fglrx] hypertorus crashed with SIGSEGV in XF86DRIQueryVersion()

[Johannes Kasch]

Binary package hint: xscreensaver

xscreensaver

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: xscreensaver-gl 5.10-3ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
Architecture: amd64
Date: Mon Apr 12 21:44:40 2010
ExecutablePath: /usr/lib/xscreensaver/hypertorus
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406)
ProcCmdline: hypertorus -root
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fb5511a512e <XF86DRIQueryVersion+174>: mov 0x4(%rax),%eax
 PC (0x7fb5511a512e) ok
 source "0x4(%rax)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xscreensaver
StacktraceTop:
 XF86DRIQueryVersion ()
 XF86DRIQueryExtension ()
 ?? () from /usr/lib/fglrx/libGL.so.1
 ?? () from /usr/lib/fglrx/libGL.so.1
 glXChooseVisual () from /usr/lib/fglrx/libGL.so.1
Title: hypertorus crashed with SIGSEGV in XF86DRIQueryVersion()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1359): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (xfce4-mixer-plugin:1400): libxfce4mixer-CRITICAL **: xfce_mixer_get_track: assertion `GST_IS_MIXER (card)' failed
 (xfce4-terminal:17649): Gdk-CRITICAL **: gdk_window_get_window_type: assertion `GDK_IS_WINDOW (window)' failed

[Apport retracing service (apport)]

StacktraceTop:
 XF86DRIQueryVersion ()
 XF86DRIQueryExtension ()
 ?? () from /usr/lib/fglrx/libGL.so.1
 ?? () from /usr/lib/fglrx/libGL.so.1
 glXChooseVisual () from /usr/lib/fglrx/libGL.so.1

[Charlie Kravetz (cjkgeek)]

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 561005, 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.