frobar: Proper handling of EOF
I now get why the Python documentation really insists you use .communicate().
This commit is contained in:
parent
465c2347cb
commit
0ac0ad1267
2 changed files with 12 additions and 1 deletions
|
|
@ -8,6 +8,9 @@
|
|||
config = lib.mkIf config.frogeye.desktop.xorg {
|
||||
boot.kernelModules = [ "i2c-dev" ]; # Allows using ddcutil
|
||||
programs.sway.enable = true;
|
||||
security.pam.services.swaylock.enable = true; # Let HM handle this
|
||||
# Otherwise the screen is locked twice, the second one with screen off
|
||||
# TODO Can we maybe use this instead?
|
||||
security.rtkit.enable = true; # Recommended for pipewire
|
||||
services = {
|
||||
blueman.enable = true;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue