Chris Rankin wrote:
--- Brian Paul <[EMAIL PROTECTED]> wrote:

Any application which depends upon the root window
having particular GLX attributes is in error.


It's a screensaver. Using the root window would seem
to be a requirement here. So what you're really saying
is "Who cares if you can't perform OpenGL / direct
rendering on the root window?". And the answer is
"Everyone who runs xscreensaver, for a start!".

Do other graphics cards have this problem?

The point is that xscreensaver is making an *assumption* that is not valid. The fact that it happened, by chance, to work in the past in no way guarantees that it will continue to work in the future. Just because you don't get in trouble for driving 100mph on the hiway once doesn't mean that you never will.


You can play semantics and say it isn't a bug,
but it is definitely a regression that will be
very unpopular with a lot of Matrox users.

I wouldn't call it a regression either.

Did work before, doesn't work now. That's the very *definition* of a regression.

Only if it's something that was supposed to work in the first place! As near as I can tell, there is no guarantee, assurance, or subtle suggestion that this would work. It was only dumb luck. :)


b) The screensavers don't segfault because there's
no suitable visual available. They seem to do so
while trying to activate the indirect rendering
instead. This is presumably why the rest of the
OpenGL hacks flash the "libGL error: InitDriver
failed" message on the screen and then run very
slowly. And segfaults are always bugs.

It sounds like there might be a broader issue here. What does 'glxinfo' report? Does glxgears run with
hardware acceleration?

In looking back at your original post, I bet I can guess what the problem is. You're running in 16-bpp, and therefore have no stencil buffer. Visual ID 0x25 has stencil buffer. The xscreensavers must require a stencil buffer. If you change to 32-bpp I bet everything will work.


Workarounds not withstanding, the xscreensaver code is not correct. If the individual screensaver modules do not need stencil buffer, the screensaver daemon shouldn't force a visual that has stencil buffer.



-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to