Package: xscreensaver-gl
Version: 5.03-2
Severity: normal
Hi,
I have several users on the same home computer, often leaving sessions open
and using KDE's Switch User to move between users; for all users, the
screen saver is set to Random. Many times, upon switching to a different
user, the CPU
1) If a GL saver is consuming 100% CPU, then that means that OpenGL
is running on the CPU and not on the GPU, in other words, it's not
using your graphics hardware at all. So you should try and figure out
why that would be.
2) There's no way for xscreensaver to realize that it's not on the
First of all, thanks for a response far faster than I expected.
On Wednesday 03 October 2007, Jamie Zawinski wrote:
1) If a GL saver is consuming 100% CPU, then that means that OpenGL
is running on the CPU and not on the GPU, in other words, it's not
using your graphics hardware at all. So you
I dug a little further in another direction: I had thought screensavers named
like Helios(GL) came from xscreensaver-gl, but (as you probably know) they
don't; they come from rss-glx.
So I checked again which savers are problematic, and it turns out to be almost
exactly the rss-glx screen
4 matches
Mail list logo
