Xscreensaver
 

Just one of many gems

I used xlockmore once. A serious downside of xlockmore is that it locks just X Window sessions. I usually run two such sessions starting X Window from two consoles with startx command. After locking X Window with xlockmore it is still possible to switch to any console using Ctrl+Alt+F[1–6] keyboard shortcuts, then use Ctrl+C to kill X Window and – finally – run unlocked session with startx command. As a result xlockmore locks nothing because anyone is able to kill locked session and start a new one.

In order to lock X Window and consoles I use vlock --new command. It locks everything completely.

Never had it, never will.
 

Amen! I use a fullscreen customized version of xdaliclock, not within xscreensaver, but stand alone.

If you use xlockmore you may define following ACPI action:

/etc/acpi/actions/fnf2-lock.sh
and an ACPI event such as:

/etc/acpi/events/fnf2-lock
Above action finds all running X Window sessions, identifies their users, and locks these sessions – users may unlock sessions using their own passwords.

Above event works with IBM/Lenovo ThinkPads.

I've been an xscreensaver user for years until a few years ago. Oneday I locked my home desktop (yes, I do that even at home, because I pretend to be a security literate user) and went out for shopping. When I returned back home, I saw that xscreensaver had segfaulted, thus had compromised the privacy of my personal files. I have switched to slock of suckless fame and never had any issues with it since then. It doesn't come with vanilla Slackware, so I'll use this opportunity to thank rworkman again for providing a slock buildscript on SBo.

Huh? I remember jwz boasting xscreensaver being one of the least segfaulty apps out there. Perhaps he's biased.

it happened to me too, with some of the GL screensavers, but I dunno if they were to blame or the nvidia drivers instead...

I didn't vote because "don't care" or "whatever PV includes" wasn't an option.

Generally, a screensaver is expected to be stable indeed. You can have fancy full disk encryption with a giant password and user passwords that are shorter/weaker (because you have full disk encryption!), then a segfaulty screensaver leaves you with pants down if it crashes.

In a well designed screensaver it shouldn't matter. The actual locker would run the demo in a subprocess and just restart it if it crashes.

PV includes both. That's the point of the survey. And that's why there are not xfce4-screensaver and other (purportedly, less secure) screensaver options.

PV includes at least 3 that I'm aware of (see below). Doing the poll this way prevents you from getting accurate results due to those who decide to use something else or choose to use nothing at all.

It's like asking Germans if they drive a BMW or Mercedes, even though there's also VW and the many other non-German options people might be driving. If you wanted to leave the poll based on what's provided in Slackware AND get an accurate idea of what people are using on the system, it should've included at least 5 options:

• xlockmore
• xscreensaver
• screenlocker (KDE Default)
• something else
• nothing

That's correct, I should have made a better question. I was actually interested in XFCE users, moreover, people who prefer to use as much stock software as possible. But that would clutter the question :-(

I need to make a new one some time later

Then I'll revise my reply here;

What ever PV decides to use by default for the stock configuration, like I setup on multiple PCs using XFCE and FVWM. (I tend to stay away from KDE, and don't even install it on at least 2 of my PCs)

To elaborate a little more, I have at least 2 PCs that run ONLY stock configurations with only slackrepo added. So in essence, my original reply is technically still correct.

But I do use Cinnamon DE on one which has it's own screensaver/screenlocker (that uses PAM and krb5 and depends on xlockmore? not really sure)

Wow, it looks like xscreensaver is winning by a landslide!

Then again, it doesn't look like there are very many people voting in this poll, anyway. Still, part of me expected the results to at least be a little closer.