[fglrx] hypertorus crashed with SIGSEGV in XF86DRIQueryVersion()

[JuanoX]

Binary package hint: xscreensaver

1) I'm using using Ubuntu 10.04 LTS Lucid Lynx
2) xscreensaver 5.10 3ubuntu3
3) I expected to be able to scroll through the screensavers without a problem
4) instead of that some of the screensavers (or the screensaver manager) have bugs or are missing.

The screensaver came on, I typed my password and a error appeared when the screen was unlocked,
then I went to - system > preferences > screensaver - and this following screensavers crash when selected to preview

gltext
hypertous
antspotlight
glblur
glcells
glmatrix
glschool
glslideshow

thanks

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: Sun Apr 11 17:02:57 2010
ExecutablePath: /usr/lib/xscreensaver/hypertorus
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
ProcCmdline: /usr/lib/xscreensaver/hypertorus -root
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f8a6671411e <XF86DRIQueryVersion+174>: mov 0x4(%rax),%eax
 PC (0x7f8a6671411e) 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

[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)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

[Charlie Kravetz (cjkgeek)]

Well, jumped the gun on confirming this bug. We will need a little more information to send this upstream to the xscreensaver developers.

f the problem is reproducible, please type the following into a shell:

      xscreensaver-command -exit
      xscreensaver -verbose -log xscreensaver-log.txt

That will re-start xscreensaver and append diagnostics to the "xscreensaver-log.txt" file. When the problem happens again, attach the xscreensaver-log.txt file to this report.

[JuanoX (juano111)]

hi! how are you? dont worry, ok so this is what I got.

1) I did run the command to restart xscreensaver but then the terminal gave a message saying that I did not have xscreensaver installed (weird because then from where did this error come from)
2) then I installed xscreensaver and it said that I had gnome screensaver (probably the source of the problem?) installed and that it had to be turned off, so I agreed.
3) I run the command to create the log file for xscreensaver
4) Tried to reproduce the problem with xscreensaver by selecting the "bad" screensavers and they appear to be installed(they are in bold letters unlike the "not-installed" ones that are in grey letters) but nothing comes on the preview window, it reads "no preview available".
5) I clicked the "preview" button and the screen went black and I could see the mouse... I had to force-shut down the computer to get out of there.

-- now I have two "screensaver" buttons under system>preferences

Other thoughts: is there a similar script but for gnome screensaver?

thank you also for your time and for helping this awesome OS ;) best regards

[Charlie Kravetz (cjkgeek)]

I only know of this for xscreensaver, since when I went to see about upstreaming the bug, this is what is required. For GnomeScreensaver, we can file the bug directly to the developers using the attached stacktrace. My guess, though, is that the bug is really in xscreensaver-GL, which means we are in the right place already. I will send this through to the developer, and see what his response is.

Thanks for taking the time to do this.