ifreund changed the topic of #river to: river - a dynamic tiling wayland compositor - https://github.com/ifreund/river - channel logs: https://freenode.irclog.whitequark.org/river/
<ifreund> leon-p: finally put up a PR for the riverctl river-options implementation though I have one more yak to shave before merging
<ifreund> let me know if you think the CLI interface does/doesn't make sense
<ifreund> we also have a small, zero-allocation arg parser thing now
g_w1 has joined #river
<g_w1> hello, I tried to build on nixos using the provided shell.nix in the wiki, but failed with a linker error: https://cdn.discordapp.com/attachments/606246764651085829/800513514732519433/message.txt
<g_w1> should I not be using latest master?
<ifreund> g_w1: you're using wlroots master, you need wlroots 0.12.0
<g_w1> ah, thx
<ifreund> np
<ifreund> Idk how nixos works, but I removed that function from wlroots master
<ifreund> and it's definitely present on 0.12.0
<g_w1> ok
<g_w1> is there a way to check what version of wlroots is installed?
<ifreund> normally I'd say ask your package manager but if we aren't trusting it you could read the wlroots headers I guess
<g_w1> oh nixos has 0.11.0, nvm. nixos master is different than 20.09
<g_w1> i will just use the master shell and ill update the wiki if it works
<ifreund> oh lol, I read the symbol name wrong. Had a couple people report that building failed with the one that got removed on master
<ifreund> the layer surface one you hit is one I added in 0.12.0 :D
<ifreund> why the hell does nixos still have wlroots 0.11.0 though? I thought they were kinda up to date?
<ifreund> or maybe that's just the unstable channel
<ifreund> and yeah feel free to update that wiki page however you see fit :)
<g_w1> its unstable, I could use it if I wanted, but im on 20.09
<ifreund> I guess the point of nix is that you can use unstable just for dev environments and stuff
<ifreund> heck, I used it for a bit to get llvm11 binaries before they were packaged for void
<g_w1> ok nice it built thx
<g_w1> yeah it was fairly easy to just download the wlroots.nix file
g_w1 has quit [Quit: Connection closed]
waleee-cl has quit [Quit: Connection closed for inactivity]
_whitelogger has joined #river
travankor has joined #river
travankor has quit [Remote host closed the connection]
trav80563 has joined #river
<leon-p> fwiw I also get the crash on exit on master, so it is not my code causing the issue.
<ifreund> leon-p: got a stacktrace for me?
<ifreund> piping stderr to a file can be helpful if it only happens on a tty
leon-p has quit [*.net *.split]
tsujp1 has quit [Ping timeout: 272 seconds]
leon-p has joined #river
tsujp1 has joined #river
<leon-p> log is here: https://paste.rs/f4y
<leon-p> actually seems like the debug code of std is crashing?
edrex has quit [Ping timeout: 240 seconds]
<leon-p> although I have no idea how `return_address - 1` could trigger an overflow.
ifreund_ has quit [Ping timeout: 258 seconds]
voroskoi has quit [Ping timeout: 244 seconds]
samhsmith[m] has quit [Ping timeout: 244 seconds]
<leon-p> stack trace by gdb is here: https://paste.rs/jG9
<leon-p> ifreund: ^
trav80563 has quit [Ping timeout: 268 seconds]
<ifreund> leon-p: are you sure you're using wlroots 0.12.0?
<ifreund> there's also the fact that you seem to be using the logind wlroots backend while I use libseat
samhsmith[m] has joined #river
voroskoi has joined #river
ifreund_ has joined #river
edrex has joined #river
<ifreund> I think I need to put an actually secure screenlocker protocol on the TODO
<ifreund> or maybe what I really want is a screensaver protocol and have the locking part be handled by the compositor
<ifreund> leon-p: debug symbols for libwayland might also shed some more light, though I assume something didn't remove its display_destroy listener before it was de-allocated
<ifreund> valgrind would probably tell us what that thing was
<leon-p> screenlockers in wlroots land currently use layer shell, don't they?
<leon-p> But yeah, something dedicated would be nice
<leon-p> I think hikari is already doing locking server-side
waleee-cl has joined #river
<ifreund> indeed, hikari handles locking server side
<ifreund> river currently has the same support for "screenlockers" as sway does, which is just layer-shell and input-inhibit
<ifreund> I think server-side is the simplest secure option, though a dedicated protocol may be able to offer the same level of security
<ifreund> I think a screensaver protocol leaving the locking itself up to the compositor is the way I probably want to go though
<ifreund> but that can come much later, the sway approach is OK enough for now
leon-p has quit [Quit: leaving]
travankor has joined #river
travankor has quit [Ping timeout: 268 seconds]