12:42 <ThatGuestAgain> Hi, I'd like to use waylock. Swaylock works perfectly for me, waylock unfortunately does not accept my password. All I can do is kill river from tty, since (as the waylock manpage says) killing waylock alone is not enough. Any ideas? (NixOS unstable, very barebones config)

12:57 <LarstiQ> ThatGuestAgain: I can confirm with `nix-shell -p waylock`. It logs `error: PAM authentication failed: Authentication failure

13:02 <ThatGuestAgain> Ah, thanks for that info. With river, the shell I started it from died too and I'm hesitant to risk my entire session again (cause maybe there is an obvious answer). Quickly looking on 'pam' (never encountered it): That is a *lot*. I have no idea why it would accept swaylock but not waylock, I have nothing configured with it.

13:05 <LarstiQ> ThatGuestAgain: I am not seeing anything obvious in https://github.com/NixOS/nixpkgs/blob/nixos-24.05/pkgs/applications/misc/waylock/default.nix#L46 so starting at https://codeberg.org/ifreund/waylock next

13:06 <ThatGuestAgain> Yeah PAM is mentioned there, I found a link to a oneliner but I don't know how I should integrate that.

13:06 <ThatGuestAgain> *ooonliner file

13:07 <LarstiQ> https://codeberg.org/ifreund/waylock/src/branch/master/src/auth.zig#L117 presumably is what logs it

13:07 <LarstiQ> ThatGuestAgain: I'd assume it's supposed to work without any additional pam customization

13:09 <ThatGuestAgain> I mean, swaylock does, so I thought it should.

13:10 <ThatGuestAgain> Oh, I might have figured it out. I'll close chat, rebuild, and lock. Wish me luck ;)

13:17 <LarstiQ> I'd wish ThatGuestAgain luck but after 6 minutes perhaps that did not work out

13:19 <ThatGuestAgain> I added that oneline file, still won't work :( In here by phone now, that may take several tries...

13:25 <ThatGuestAgain> Huh, the error ends not with failure, but "permission denied". I'm confused. Yes the password is right, I've tried often enough :D

13:27 <tiosgz> ThatGuestAgain: both swaylock and waylock need a file in /etc/pam.d -- it should be installed with waylock normally, but here some nix weirdness may be breaking it

13:28 <tiosgz> anyway, just joined and going out. hope you can figure it out

13:34 <adamcstephens> ThatGuestAgain: do you have this in your nixos config? security.pam.services.waylock = { };

13:34 <adamcstephens> if not, you do need it 😉

13:38 <ThatGuestAgain> Oh... I was trying to figure out how to put the proper things into etc via environment.etc.path... Anything required inside {} adamcstephens?

13:38 <adamcstephens> no

13:38 <adamcstephens> i think i may see why waylock doesn't work and swaylock does, out of the box, but you can work around it with that line above.

13:40 <adamcstephens> https://codeberg.org/ifreund/waylock/src/commit/0f355a9fa61bfa775cc9484c0470df610320b9ac/pam.d/waylock

13:41 <adamcstephens> nixos doesn't have a `system-auth` pam service

13:42 <ThatGuestAgain> Thank you so much, got it working!

13:46 <ThatGuestAgain> Yeah that file was what I added to etc...

13:48 <adamcstephens> swaylock uses `login` which does exist, which is why it works. we'll have to patch the waylock file on install. i'll add it to my todos.

13:54 <LarstiQ> adamcstephens: cheers!