Bug 7691 - GL screensavers crash
Summary: GL screensavers crash
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: xscreensaver
Version: 1.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-12-08 23:19 UTC by Brian Ryner
Modified: 2014-03-17 02:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2000-01-18 17:00:49 UTC

Attachments (Terms of Use)

Description Brian Ryner 1999-12-08 23:19:32 UTC
I'm not sure if this is a problem with xscreensaver or with glxMesa.
Whenever I try to use one of the GL screensavers (I tried with atlantis and
bubble3d), it segfaults.  I got the following stack trace from gdb:

Program received signal SIGSEGV, Segmentation fault.
0x40032d4a in glx_send_client_info () from /usr/X11R6/lib/libGL.so.1
(gdb) where
#0  0x40032d4a in glx_send_client_info () from /usr/X11R6/lib/libGL.so.1
#1  0x40058708 in ?? () from /usr/X11R6/lib/libGL.so.1

I'm running XFree86-3.3.5-15 (SVGA server), Diamond Viper 330 (Riva128).

Comment 1 Bill Nottingham 1999-12-08 23:29:59 UTC
You need to add:

Section "Module"
        Load "glx.so"

to your /etc/X11/XF86Config (and restart the server, of course).

Dunno how well the Riva128 is supported by the new glxMesa stuff.
(only testing here has been with G200).

Comment 2 Bill Nottingham 1999-12-08 23:30:59 UTC
Yes, the glx stuff should probably exit more gracefully
if the server module isn't there, though...

Comment 3 Brian Ryner 1999-12-09 01:00:59 UTC
That didn't work... it caused X to crash on startup with this error:

Fatal server error:
Caught signal 4.  Server aborting

When reporting a problem related to a server crash, please send
the full server output, not just the last messages

X connection to :0.0 broken (explicit kill or server shutdown).

Comment 4 Bill Nottingham 1999-12-09 17:40:59 UTC
What processor do you have?

Comment 5 Brian Ryner 1999-12-09 17:43:59 UTC
Pentium/MMX 233 MHz.

Comment 6 Bill Nottingham 1999-12-15 21:50:59 UTC
Out of curiousity, what happens if you rebuild the SRPM
and install it on your own machine?

Comment 7 Bill Nottingham 1999-12-15 21:51:59 UTC
(that's the glxMEsa source RPM.)

Comment 8 Brian Ryner 1999-12-17 23:36:59 UTC
Well, I rebuilt from the 19991206-3 SRPM, and I have a question regarding your
previous instructions to add:

Section "Module"
        Load "glx.so"

to XF86Config.  Now, this file is only in the -devel RPM.  Shouldn't that go in
the main package RPM?

Comment 9 Brian Ryner 1999-12-18 00:00:59 UTC
By the way, rebuilding the package on my machine seems to have solved the
segfault.  Unfortunately, it looks like I'm not getting accelerated 3d on my
Riva128.  I'm going to look into that, it looks like there is some support in
glxMesa that can be turned on.

Comment 10 Bill Nottingham 1999-12-20 18:59:59 UTC
OK, looks like the configure script is being stupid and
specifying -march=i686 when built on a PII/PIII (which
our build machine is...).

We'll get this fixed. Possibly we should build both i686
and i386 packages.

Comment 11 Bill Nottingham 2000-01-18 17:00:59 UTC
This has been fixed in the glxMesa packges, and in the
distribution as the latest Raw Hide ships with software
Mesa only.

Note You need to log in before you can comment on or make changes to this bug.