15:47 <gplxyz> Hey everyone :)

15:47 <gplxyz> out of curiosity: anyone here heard of someone running river on freebsd? i have about 20hours of "progress" and nothing but a default wallpaper, cursor and nothing else works. constant logs of wlroots not being able to connect to any client, but of course nothing to be found on that:D

16:00 <aelius> gplxyz: this is an (educated) guess: do you have seatd running?

16:01 <gplxyz> yeah. i do :(

16:01 <gplxyz> dbus, seatd both enabled

16:02 <aelius> welp I'm no help then :]

16:02 <gplxyz> i can login, it shows a wallpaper and a cursor.

16:02 <gplxyz> so i assume it is technically working, but not able to properly get/send client info

16:03 <gplxyz> anyway. ty so much for the try :D

16:04 <aelius> you should share your river init, others might want to see it

16:04 <Nickli> what terminal do you have it set to start?

16:05 <gplxyz> alacritty, kitty, foot. nothing wokrs. the init is only keybinds.

16:05 <gplxyz> anyway. will try some shit and report back

16:07 <aelius> i don't have enough info to file a useful report, but perhaps this is known: moonlight gamestream seems to cause river to misbehave then crash

16:09 <aelius> Specifically, river stops being able to change which window is active (even after moonlight exits), and eventually river crashes as I flail around trying different things

16:10 <aelius> also notably, river seems to not support the way in which moonlight tries to take exclusive input control

17:50 <leon-p> aelius: what river version are you running? those sound like pretty ancient river bugs

17:52 <aelius> hmm, should be whatever arch repos gave me

17:53 <aelius> I'll check when I can

17:54 <leon-p> either way, would it be possible for you to build river from git master branch and check if the bugs still persist?

17:54 <aelius> yep