<xaltsc>
Hey, this is slightly off topic, but given that ifreund is the manager, I might as well ask here/report it: when I unplug the HDMI cable, waylock blocks.
<ifreund>
xaltsc: what river version and waylock version are you using?
<xaltsc>
river 0.3.3 (via nix); waylock 0.6.3 via xbps
<ifreund>
and what do you mean by blocks exactly?
<xaltsc>
I also probably don't know how to kill waylock. When in this kind of situation (for instance, waylock provided by nix/hm doesn't interact well with pam and can't unlock), I used to switch to another tty and just kill waylock. Idk if this is linked to having switch from seatd to elogind, but this doesn't work anymore.
<xaltsc>
ifreund: the screen goes black and entering the password doesnt close waylock
<ifreund>
xaltsc: ah, actually update your waylock version
<ifreund>
xaltsc: maybe get waylock from nix as well then
<ifreund>
void's ability to package an up to date version of zig doesn't seem likely to improve any time soon
<ifreund>
alternatively, grab a static zig binary from ziglang.org/download and build waylock from source
fitrh has quit [Remote host closed the connection]
<xaltsc>
ifreund: the problem with nix's waylock is that it doesn't seem to connect with PAM (it's a general issue when nix installed stuff needs to interact with local libraries), I haven't found a way to solve it and everyone seem clueless about it
<ifreund>
xaltsc: you sholud just need to adjust the /etc/pam.d/waylock file to use the proper value for your system
<ifreund>
presumably that's not compatible with void's PAM configuration though
<ifreund>
void seems to use system-auth, so if you just undo that patch from nix it should work
<xaltsc>
ifreund: doesn't that stuff from the nix recipe just write a pam.d/waylock file ?
<ifreund>
I don't think so?
<ifreund>
It looks to me like it patches the pam.d/waylock file shipped with waylock
<ifreund>
because nixos presumably uses login rather than system-auth in their PAM config
<xaltsc>
But would waylock (from nix) (or PAM, idk which does what) use /etc/pam.d/waylock (i.e. void's file) ? Maybe I should have insisted on the fact that I only use home-manager, so as far as I understand it, nix control over my environment is limited to setting variables on login.
<xaltsc>
wouldn't
<ifreund>
I can't help you with nix specifics, you're on your own there
<ifreund>
it seems like tweaking the PAM config would be worth a try though
<xaltsc>
I guess my question isn't that nix specific: when waylock launches, is it its job to select the pam configuration, or is it pam that allows waylock to do stuff ?
<xaltsc>
(i.e. will it use nix's pam.d/waylock or void's one)
<ifreund>
waylock asks the libpam library it is linked against to authenticate the "waylock" pam service
<xaltsc>
ok, so what you say makes sense
<xaltsc>
btw, any idea how I might kill waylock from another console when it is stuck ?
<ifreund>
killall waylock?
<xaltsc>
As I said, I guess it interacts with elogind and session/seat lock, but idk, I haven't tried to unlock the session before killing waylock
<ifreund>
if you're actually asking how to unlock your river session after waylock has crashed, you can start a new waylock or swaylock instance
<xaltsc>
ifreund: that doesn't work anymore :D
<ifreund>
e.g. WAYLAND_DISPLAY=wayland-1 waylock from a different tty
<xaltsc>
clever
<xaltsc>
and that solves the issue when the HDMI cable is unplugged as well, thanks
<xaltsc>
The problem seems to be figured out in the current version, but I guess waylock was just crashing when the HDMI cable was unplugged
<ifreund>
it was comitting a protocol error and exiting
<ifreund>
and this was fixed long ago
lbia has joined #river
<xaltsc>
I think I got rid of the preBuild argument, however it still doesnt work. I'm getting "error: PAM authentication failed: Authentication service cannot retrieve authentication info"
<ifreund>
I wouldn't be surprised if nix also patches libpam
<xaltsc>
ugh
<ifreund>
I can't really help with artificial problems created by using nix sadly
<ifreund>
compiling waylock from source using a statically linked zig binary from https://ziglang.org/download is probably the easiest path to take at this point
<xaltsc>
I'm fine with having an older version anyways, and especially now that I have a solution that does not require to power down the computer
haasn has quit [Ping timeout: 255 seconds]
mattnite has quit [Ping timeout: 255 seconds]
switchy has quit [Ping timeout: 256 seconds]
Anderson-D has quit [Ping timeout: 256 seconds]
bw_______ has quit [Ping timeout: 255 seconds]
yongxiang has quit [Ping timeout: 256 seconds]
haasn has joined #river
Anderson-D has joined #river
yongxiang has joined #river
mattnite has joined #river
bw_______ has joined #river
switchy has joined #river
hush has joined #river
<adamcstephens>
The patched pam file in the nix package only ends up in the package itself. On non nixos this wouldn't be used without extra effort
<adamcstephens>
I would expect you could just symlink /etc/pam.d/waylock -> /etc/pam.d/system-auth manually and then use the nix package, but I haven't tried it
<adamcstephens>
pam files for nix are in the standard location of /etc/pam.d
<adamcstephens>
(e.g. not patched to change that)
<ifreund>
yeah, then I see no reason this wouldn't work with correct manual pam configuration
lbia has quit [Quit: lbia]
lbia has joined #river
leopoldek has joined #river
hush has quit [Quit: WeeChat 4.3.2]
<xaltsc>
adamcstephens: wouldn't that just do the same thing as having auth include system-auth in pam.d/waylock ?
<adamcstephens>
it should yes
<xaltsc>
so it wouldn't change a thing :D
kaleb has joined #river
kaleb has quit [Quit: leaving]
waleee has joined #river
hspak1 has joined #river
hspak has quit [Read error: Connection reset by peer]
hspak1 is now known as hspak
leopoldek has quit [Ping timeout: 246 seconds]
leopoldek has joined #river
walee_ has joined #river
waleee has quit [Ping timeout: 264 seconds]
walee_ has quit [Ping timeout: 252 seconds]
angry_vincent has quit [Ping timeout: 255 seconds]