From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: kiasoc5 <kiasoc5@disroot.org>
Cc: Christine Lemmer-Webber <cwebber@dustycloud.org>, help-guix@gnu.org
Subject: Re: What are you doing for a screen locker?
Date: Sun, 22 Jan 2023 20:17:57 -0500 [thread overview]
Message-ID: <87ilgyyrp6.fsf@gmail.com> (raw)
In-Reply-To: <9e39a01b-3c91-238c-68a0-49a6f2760a55@disroot.org> (kiasoc5@disroot.org's message of "Sat, 21 Jan 2023 14:54:50 -0500")
Hi,
kiasoc5 <kiasoc5@disroot.org> writes:
> On 1/21/23 13:44, Christine Lemmer-Webber wrote:
>> I used to use xscreensaver. I kinda miss it. It's still broken, see
>> bug #57919.
>> But really, the lack of xscreensaver has made me move back to Gnome
>> and
>> recently Gnome started having weird bugs on my hardware, so then I
>> wanted to move back to stumpwm. But I simply don't understand how to
>> get screen locking to work right without xscreensaver, which at least
>> had made it relatively easy.
>> The cookbook contains some info on how to use session locking with
>> xorg
>> but it doesn't seem like complete information. I'd be interested if
>> people would share their configurations. Thanks!
>>
>
> xlockmore and slock are installed in %base-packages and should work
> out of the box on Xorg.
I use xlockmore, but beware that it'll peak one of your core 100% while
used. Perhaps there's something better?
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-01-23 1:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 18:44 What are you doing for a screen locker? Christine Lemmer-Webber
2023-01-21 19:54 ` kiasoc5
2023-01-23 1:17 ` Maxim Cournoyer [this message]
2023-01-23 1:24 ` Benjamin Slade
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilgyyrp6.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=cwebber@dustycloud.org \
--cc=help-guix@gnu.org \
--cc=kiasoc5@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).