From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830
Description of problem:
After upgrading from Red Hat 7.1 to 8.0 on my 166 mHz Pentium II, menu display
became progressively slower; this was accompanied by prolonged blanking of the
screen during refresh, sometimes with the screen saver appearing for a few
seconds before refresh succeeded.
Also, I noted that the capslock light went on 2-3 seconds after the capslock key
was pressed on one of these occasions.
The problem progressed rapidly if a lot of windows were opened an closed during
a session, especially using Open Office; but it also progressed slowly while the
system was left on overnight.
Rebooting the machine temporarily resolves the slowdown.
Others with faster machines have reported to me that they also see a slowdown,
or that xcreensaver takes up to 50% of cpu time, and disabling the screensaver
resolves the performance issue.
The the problem was solved disabling the screen saver.
During this time, I noted that the power management function of the screensaver
applet (xscreensaver-demo -crapplet) cannot be made to function.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Hat-> Preferences -> screensaver -> random screensaver
2. Do some work
3. Reboot before the system becomes non-functional
Actual Results: Same thing
Expected Results: Proper function
Are you using GL-using screensavers?
I'm using the screensavers out of the box; nothing added or installed otherwise;
the system began as a 5.x, then 6.x, then 7.1 (which was, I think, a complete
reinstall), and now upgraded to 8.0. Screensaver and dpms worked with 7.1
My habit has been to choose "random screensaver" and to select dpms to put the
screen to sleep after 1 minute of inactivity.
I do recall that there was a problem with the random screensaver 7.2 on my IBM
Thinkpad T23 causig a problem with display freezing (as I recollect) that was
solved by selecting a single screensaver display. dpms works properly there.
Given the age of this report and the lack of activity, it seems very
likely that this bug has been corrected. I'm going to close this bug,
but if you see problems with FC3 or a recent version of xscreensaver
or X, please feel free to reopen.
Correct. I have not seen this problem with FC1