Comment 2 for bug 174191

Actually you may very well be correct on my second part of the problem. However I am not sure why that makes it less a bug because it only lasts for 30 minutes before it goes to sleep ? why on earth would an application designed to be "green" friendly race the CPU until it goes to sleep ?

Second, I already know that I need to select a more PC friendly screen saver, thats why I have reported the bug (doh ! ) ( :P ), however the less curious people that are just now switching to linux will have no clue that the screen saver they selected is racing the CPU unless the have learned the TOP command or know that a CPU system monitor is available AND that it is not normal for a CPU to race when NOT being used. - most people don't know that %100 CPU is not good, and most people would not know that it is happening either.

3rd, hummm, while I have been using Ubuntu for 3+ years now, I have never been able to get xscreensave to work, I have no desire to be a linux guru, or expert, just skilled enough to configure use, minor repairs, etc. My first choice for a screensaver is ElectricSheep, thats the only screen saver I want and it requires xscreensaver, and I have never been able to get it to work even though its in the repo, which leads to a second problem, if its in the repo, then it should work, but after doing much research, it looks like the only people that are capable of making ElectricSheep work on a Gnome system are the Linux gurus.

4th, I have no clue what rss-glx is, but once again, why would removing this fix the 100% CPU racing problem ? it will still be there in the code will it not ? it will just remove the problem from my computer if you are correct, but the bug will still exist in the code. (doh again ! )

So, just to be clear, I am trying to report a bug in the bug reporting forum, not find a work around to a problem....... :) but thanks for confirming the problem , hehehe,