this post was submitted on 14 Mar 2025
19 points (100.0% liked)

Linux

52095 readers
1466 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

I have an older laptop so no need to worry about the stupid Modern Standby introduced in late 2019. What I want is a reliable way to lock screen when suspend, doesnt matter how bloat or minimal.

First, to make sure the laptop suspends when I close the lid:

  • on some Distro, this works OOTB.
  • If it doesnt, I check /etc/systemd/sleep.conf and set allow Suspend from there.

After this, laptop does suspend. Now here comes the trickiest part, how to make sure your screen stays locked? There are so many rabbit holes so I want some help.

Depending on your software selections, you can fall into 3 categories:

  1. create some systemd script like this: https://wiki.archlinux.org/title/Slock

Problem: sometimes the screen doesnt get locked, i.e. your slock doesnt get triggered. Even worse, in some cases, the desktop is briefly shown on resume, before the locker shows up.

  1. use program like xss-lock, xautolock. Then links it with your locker and then autostart in your wm. Eg: i3wm with i3lock and xss-lock:

exec --no-startup-id xss-lock --transfer-sleep-lock -- i3lock

This works. But the laptop sometimes takes a while to suspend.

  1. manually invoke "Lock" with a keystroke. Then close the lid. Apparently this works but I have to remember to manually "lock" every single time.

Thanks for any suggestions.

top 5 comments
sorted by: hot top controversial new old
[–] juipeltje@lemmy.world 4 points 5 days ago (1 children)

I recently finally configured my lockscreen again after switching to wayland. I'm using gtklock and so far it has been working really well. I'm using void linux with elogind installed, laptop suspends when closing the lid ootb. In order to trigger the lockscreen on suspend, i'm using a script placed in /etc/elogind/system-sleep, as described on the artix wiki

[–] mazzilius_marsti@lemmy.world 1 points 5 days ago (1 children)

hmm thanks i'm gonna try that script you linked in artix wiki. Havent seen that one before so its worth a shot. What I usually see is some systemd Unit scripts. Gtlock looks neat as well, does swaylock give you problems too?

[–] juipeltje@lemmy.world 1 points 5 days ago

I haven't tried swaylock unfortunately, gtklock is the first wayland screenlocker i tried. Before that i think i was using i3lock-color on xorg, which also worked fine as far as i can remember, but the problem with xorg screenlocking is that it isn't actually very safe. Also, i'm not sure what distro you are using, but if it is a systemd distro there is probably a better way to trigger the screenlocker. I'm not sure if that script works in that case because it might be elogind specific. elogind is used on distros like artix and void because they don't use systemd. Elogind is basically just the logind part ripped out of systemd.

[–] mazzilius_marsti@lemmy.world 4 points 6 days ago* (last edited 6 days ago)

The only robust and no BS lock combo so far, imo, is Regolith i3wm.

For some reasons and whatever black magic eas used, this Frankenstein combo of i3 and GNOME work every single time. The downside is their configs are soooo messy. It is very hard to use whatever you have in vanilla i3 for Regolith.

[–] poinck@lemm.ee 2 points 5 days ago

I have used xss-lock with i3lock in the past with success. It makes sure that systemd-logind notifies over dbus when entering hibernation so that xss-lock starts the configured lockscreen.

Before that I had a script which locks manually and then calls systemctl hibernate.

Currently I am on Gnome, but I want to transition back to a more minimalistic DE like niri. Then I have to look on the options again to reliably lock my screen.