From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
Description of problem:
The screensaver which "flies" you through a wire-drawn corkscrew takes about 20
to 30 seconds to exit, from the point where you touch the mouse. This is on a
Celeron 500, which really should be able to just exit within a second...
Note: I'm not sure if this happens with every screensaver, but it is quite
possible. Very annoying bug.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. grab a drink from the fridge, talk to colleagues on the way back
2. see that screen has the screensaver running
3. move mouse all over the place, madly whack keyboard, etc...
Actual Results: it looked like the machine was no longer reacting to any user
input, the screensaver just kept going and going and only exited after 30
seconds or so
Expected Results: the screensaver should have exited immediately, within a second
This is on a machine with software GL support only, correct?
yes, I suspect this is software GL handling only ... glxinfo gives:
OpenGL renderer string: Mesa DRI G400 20020221 AGP 1x x86/MMX
OpenGL version string: 1.2 Mesa 4.0.4
(and some more info)
However, that still doesn't make it acceptable for the screensaver to take 30
seconds to exit ...
That renderer string implies it is using HW GL support.
30 seconds is indeed unacceptable. It must be some mga DRI hardware accel
issue or DRM issue. Is this occuring while using our official kernel?
(yes I know our kernel sucks, but bear with me) ;o)
Can you attach X server log, config file and kernel log to peek at?
Also, completely unrelated, but I notice you're using AGP 1x only. If your
CMOS allows changing of AGP mode to AGP 2x and/or 4x, I recommend changing
it there, and then matching it in the X config file with:
Option "AGPmode" "4"
Closed, no response.