> Note that the high CPU usage is often (always) due to lack of
> functionality in the graphic card drivers, and not to bugs in
> xscreensaver. We rely on our own testing on different hardware and of
> reported bugs about high CPU usage. This has not been very systematic
> but as often in distribution packaging, a compromise between time
> invested and getting "most" things to work for "most" people.

As I said, if any of the screen savers exhibit high CPU in their default
configuration, then I consider this a bug in the saver.  The only way this
is going to get fixed is if you report it to me (or submit a patch with
appropriately-scaled-back default timings.)

The one (large) exception to this is the OpenGL savers -- obviously
those are going to be a problem on any machine that does not have
working 3D acceleration.  But, on such a system, *all* of the
OpenGL savers will be equally problematic, so uninstalling
xscreensaver-gl is presumably the right fix; no need for -gl-extra.

> Since we are providing a Linux distribution, the end user experience
> is what counts.

Fair enough, but I would like to fix the problems that lead to
degraded user experience rather than just throwing the
screen savers out with the bathwater...


--
Jamie Zawinski       j...@jwz.org                  http://www.jwz.org/
                    j...@dnalounge.com      http://www.dnalounge.com/
                                         http://jwz.livejournal.com/




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to