00:16 <NickH> ifreund: thanks for the hint. I'm actually happy with my waybar setup, was just checking for boombim

02:43 <plumeus> I'm in a weird situation. I can't seem to build NixOS's River or Waylock package even though I can download the substitutes (pre-built packages) from their repo

02:43 <plumeus> I see (core dumped) zig build -Drelease-safe -Dcpu=baseline -Dman-pages --prefix $out install with Zig 0.10.x and not 0.9.x

02:43 <plumeus> Seems like a NixOS issue but it still feels bizarre.

02:46 <tleydxdy[m]> I dig into the river crash I was seeing, in XwaylandView.handleMap the view is seemingly invalid

02:46 <plumeus> /nix/store/3yfs41f4b60jya2gk6xikx4s97zsxjr0-stdenv-linux/setup: line 1574: 22 Illegal instruction (core dumped) zig build -Drelease-safe -Dcpu=baseline -Dman-pages --prefix $out install

02:46 <tleydxdy[m]> the view have wlr_output = 0x1

02:54 <plumeus> I think I hit https://github.com/NixOS/nixpkgs/issues/214356

03:06 <tleydxdy[m]> I added some debug prints, see where the bad output came from

03:15 <tleydxdy[m]> https://github.com/riverwm/river/blob/master/river/Server.zig#L260 hmm here is it legit? the compiler seems to think const output is a Output rather than a *Output

03:16 <tleydxdy[m]> ah nvm

07:13 <ifreund> plumeus: guessing that the real problem there is nix not setting -DZIG_TARGET_MCPU=baseline when building zig

07:14 <plumeus> Yeah, seems like it.

07:19 <ifreund> tleydxdy[m]: you might try to reproduce it under valgrind. How reliably can you reproduce it?

11:56 <angry_vincent> looking into waylock. can be it be also used from river's init ?

12:21 <p00f1> ? you just use the waylock command, nothing in init

12:26 <angry_vincent> i understan it can be run as is

12:38 <tleydxdy[m]> ifreund: once a day :(

12:43 <tleydxdy[m]> right now I'm trying to access the bad pointers early to hopefully get a fault that's useful

16:03 <angry_vincent> ok, so i trying waylock, and it gives black screen with cursor. nothing happens. i tried typing my regular user password but nothing happens at all

16:10 <waleee> pretty sure you might have missed to configurate the necessary pam-stuff

16:11 <angry_vincent> it is on FreeBSD, i tried port, by my request, provided here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269320

16:13 <waleee> angry_vincent: freebsd also uses pam afaik

16:13 <angry_vincent> yes

16:13 <waleee> it's only the location of pam.d that's different

16:14 <waleee> did you chuck https://github.com/ifreund/waylock/blob/master/pam.d/waylock into /usr/local/etc/pam.d ?

16:14 <angry_vincent> it is there

16:15 <angry_vincent> i may try newer patch, provided in bug report

16:17 <waleee> the patch had a note on why it fails

16:30 <angry_vincent> i tried the very first patch. i will try newest one

16:57 <waleee> the 2nd and 3rd patch has the freebsd specific pam-stuff

17:00 <angry_vincent> yes

21:00 <angry_vincent> ifreund: i still getting just black screen with waylock. nothing happens if i type password. it is on FreeBSD. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269320

21:08 <angry_vincent> ifreund: it gives segfault, actually. i suspect that that baseline cpu argument is not correctly set in port

21:10 <angry_vincent> -Dcpu=${CPUTYPE:Ubaseline} this one

21:19 <angry_vincent> ifreund: https://bpa.st/LXXNY

22:38 <ifreund> SIGSYS is not a segfault, does freebsd have some strace equivalent that you could use to get more info? or perhaps a stack trace from gdb?