On Thu, 27 Jul 2017 10:55:23 -0400 Greg Wooledge <wool...@eeg.ccf.org> wrote:
> On Thu, Jul 27, 2017 at 07:35:24AM -0700, Patrick Bartek wrote: > > Or do what I did: dispense with a screensaver entirely. Haven't > > used one in years. Waste of CPU cycles. Besides modern computer > > screens don't even need them anymore. They aren't prone to image > > burning like tube-type monitors were. I just use xset or a power > > management utility, if installed, to "sleep" the monitor display > > after a set time of system idleness. Works great. > > For many of us, the primary function of the screen saver isn't the > prevention of image burn-in, but rather the locking of the session to > prevent other people from taking control when we step away. Maybe, for "many," but I think "most" use them because they are used to them, and the "cool" pictures and designs they display. Security is secondary. > Personally I use i3lock for this. Nice and simple. I don't use any > kind of automatic invocation or idle checking. I just manually run it > when I'm about to step away. (Used to use xlock, from xlockmore, but > that was removed from Debian several releases ago.) I lock my screen manually, too. Much of my work involves studying what's on the screen without any input. It's an annoyance when it "blanks" and I have to log back in disrupting my train of thought. That's why we have so many choices and configurations. B
