b9e0a682ab
I have a suspicion that some systemd bugs around this feature (I actually couldn't figure out what it does and why?) introduced in systemd 256 lead to issues with suspend that I've seen in recent times. In the issue, my machine is seemingly frozen after resuming from suspend. I'd seen this previously on EXWM with xsecurelock, but now I'm seeing it on niri with swaylock, where it is more severe because switching to a VT is impossible. Upstream tickets: - https://github.com/systemd/systemd/issues/33083 - https://github.com/systemd/systemd/issues/33626 - https://bugzilla.redhat.com/show_bug.cgi?id=2321268 I'm not running a VM, but there seem to be multiple different bugs leading to this, so who knows. It's worth a try. The long-term fix will be getting rid of systemd) Change-Id: Ie985a3f222f3daac1e3c7db79ee8624c66297374 Reviewed-on: https://cl.tvl.fyi/c/depot/+/12961 Autosubmit: tazjin <tazjin@tvl.su> Reviewed-by: tazjin <tazjin@tvl.su> Tested-by: BuildkiteCI |
||
|---|---|---|
| .. | ||
| arbat | ||
| camden | ||
| frog | ||
| khamovnik | ||
| koptevo | ||
| modules | ||
| tverskoy | ||
| zamalek | ||
| .gitignore | ||
| default.nix | ||
| README.md | ||
NixOS configuration
My NixOS configurations! It configures most of the packages I require on my systems, sets up Emacs the way I need and does a bunch of other interesting things.
System configuration lives in folders, and some of the modules stem
from //ops/modules.
Machines are deployed with the script at ops.nixos.rebuild-system.
Configured hosts:
tverskoy- X13 AMD that's travelling around with mefrog- weapon of mass computation (in storage in London)camden- NUC formerly serving tazj.in (in storage in London)