Bug 85897 - screensaver takes 20+ seconds to exit
Summary: screensaver takes 20+ seconds to exit
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: xscreensaver
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2003-03-10 15:47 UTC by Rik van Riel
Modified: 2014-03-17 02:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-07-30 23:25:20 UTC

Attachments (Terms of Use)

Description Rik van Riel 2003-03-10 15:47:26 UTC
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):

How reproducible:
Didn't try

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

Additional info:

Comment 1 Bill Nottingham 2003-03-10 21:32:30 UTC
This is on a machine with software GL support only, correct?

Comment 2 Rik van Riel 2003-03-10 22:35:25 UTC
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 ...

Comment 3 Bill Nottingham 2003-03-10 22:43:59 UTC

That renderer string implies it is using HW GL support.

Comment 4 Mike A. Harris 2003-03-11 02:07:50 UTC
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"


Comment 5 Bill Nottingham 2003-07-30 23:25:20 UTC
Closed, no response.

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