Thanks. I will try that. My monitor has not been going into standby when the screensaver kicked in, and I assumed that the monitor was registering the screensaver as an active use of the screen. The monitor does go into standby when I am in console or when there is no one logged in and just the login prompt is showing. So, using xlock could be just the ticket Theo. Sean Schulze theodore.schulze@us.army.mil

You can use xlock. You do not have to associate an screen saver with xlock and still have it lock your screen. Also even with xlock on the apmi should still kick in and auto suspend your monitor. Hope this helps.

Austin Morgan

On Wed, Oct 23, 2002 at 02:40:57PM +0200, theodore.schulze@us.army.mil wrote:

...

Silviu Marin-Caea wrote:

...

Clayton Cornell wrote:

...

That solved my lockups with 8.0 just before I installed 8.1 Don't> > > know why but xscreensavers and my machine did not get along at all.

Screensavers have been invented in the old times, when computers couldn't turn off automatically the monitor after some idle time.

The monitor would display the same image for hours, if left unattended. This caused damage to the fluorescent particles of the monitors from that past time. Screen-savers were invented for this reason, to show a moving image that would even the usage of screen surface.

Nowadays, computers can turn off the monitor. Sorry, but this fact alone should be killer for the whole screen-saver type of application.> >

Well, I don't have a screen-saver aquarium, but I do like the feature of having my screen password protected. How do you put the monitor into standby and have it password protected without the utility of a screen saver? (Not trying to be "in your face" about this; just curious what you use.)

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com