OpenGL screensavers cause crashes

StacktraceTop:?? ()
init_GL (mi=<value optimized out>) at xlock-gl-utils.c:91
init_planet (mi=0x8c3450) at glplanet.c:483
xlockmore_init (dpy=0x63e9a0, window=8388990, xlmft=<value optimized out>)
main (argc=1, argv=<value optimized out>) at screenhack.c:570

Unless you can reproduce with the open-source drivers, I am inclined to believe this is the fault of the fglrx driver. Can you please attach Xorg.0.log so we get all the details of the hardware?

Your card is supported by the -ati open-source driver. Can you please try it?

Hi Brian,

There is a new -fglrx 8-01 uploaded last night; when you get a chance can you please re-test against that? If it crashes again, please attach your /var/log/Xorg.0.log, /etc/X11/xorg.conf, and the output of lspci -vvnn. Also, does glplanet always reliably cause the crash? If not, can you outline whatever steps are involved in making it crash?

There are about a dozen xscreensaver bugs that look to possibly be dupes of this. At least, they smell similar. All seem to involve GL crashes on amd64 with fglrx:

https://bugs.edge.launchpad.net/ubuntu/+source/xscreensaver/?field.searchtext=fglrx&orderby=title

Note that there are also a bunch of similar bugs against nvidia.

Brian, if you have bughelper handy, you could probably mass-dupe all those xscreensaver bugs to this one.

Ted Gould, since this is a major bug for xscreensaver, I figured you will want to track this as well so have subbed you.

tedgagnon, oops sorry, I meant to sub Ted Gould and entered "tedg" without thinking, and it subbed you - unfortunately I don't think I can correct that mistake; please unsub yourself and accept my major apologies.

I too am experiencing this bug. With Kubuntu 8.04 (AMD64), certain GL screensavers will crash using the fglrx driver. I've reverted to just using a slideshow screensaver (the kids prefer it anyway) while I'm also coping with fglrx bug #118605 (https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/118605)

I currently have the following package versions installed and have not been able to create a crash with a GL screensaver. I've tried previewing them, previewing them in fullscreen, and locking my dekstop for a wee bit and unlocking it without any problems.

linux-restricted-modules-2.6.24-16-generic:
  Installed: 2.6.24.12-16.34

xscreensaver-gl-extra:
  Installed: 5.04-4ubuntu1

Description: Ubuntu 8.04
Release: 8.04

attunel crashed with SIGSEV

I think it is because of the new fglrx drivers (the ones with aiglx support). Hope they get them to work properly soon.

spacetree it'd be helpful to know which particular new fglrx drivers you are using could you provide the exact package version of linux-restricted-modules you have installed? You can find this out via 'apt-cache policy linux-restricted-modules'.

linux-restricted-modules:
  Instalados: (ninguno)
  Candidato: 2.6.24.16.18
  Tabla de versión:
     2.6.24.16.18 0
        500 http://mx.archive.ubuntu.com hardy/restricted Packages

Hope this helps

I can confirm a very similar issue (reported as bug #200804): if using two displays every GL screensaver is _very_ slow and hangs nine out of ten times when I move the mouse/hit a key instead of showing me the password dialog to unlock my screen. It happens only to GL screensavers.
Logging in remotely and killing the screensaver gives my desktop back.

using current 8.04

00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)

Good day Brian,

I've just uploaded a new 8.543 version of -fglrx to Intrepid which now should work with xserver 1.5. Would you mind testing this new version and reporting back whether this issue is still present? If it is, it would be helpful if you could (re-)post your Xorg.0.log from running with this version. Thanks ahead of time.

If you don't have Intrepid installed on your system, you can test this by booting an Intrepid LiveCD (available from cdimage.ubuntu.com), using either the -vesa or -ati driver, then update to the latest version of Ubuntu, install fglrx, and then logout and back in. Your /var/log/Xorg.0.log will confirm whether you've loaded FGLRX successfully.

If you find any new issues, please report them as separate bugs. You can use the tool `ubuntu-bug fglrx-installer` which will gather the necessary files and create the launchpad report for you to fill in more easily.

ping? Is anyone still seeing this issue on Intrepid? Otherwise we'll close it as expired.

I haven't seen this bug in a while, but after upgrading to the latest Jaunty version (8.522 is it?) it seems to have reappeared. In particular, MPlayer using the gl2 video output frequently locks up the screen and X entirely, necessitating a hard reboot.

Please let me know what info you need.

> Please let me know what info you need.

A fresh Xorg.0.log[.old] from after reproducing the issue, output from 'lspci -vvnn', and a full backtrace (directions are at http://wiki.ubuntu.com/X/Backtracing). Thanks ahead of time.

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.