ifreund changed the topic of #river to: river - a dynamic tiling wayland compositor || https://github.com/riverwm/river || channel logs: https://libera.irclog.whitequark.org/river/
notzmv has quit [Ping timeout: 240 seconds]
mon_aaraj has quit [Ping timeout: 268 seconds]
mon_aaraj has joined #river
notzmv has joined #river
snakedye has quit [Ping timeout: 240 seconds]
snakedye has joined #river
snakedye has quit [Ping timeout: 240 seconds]
snakedye has joined #river
mon_aaraj has quit [Ping timeout: 250 seconds]
mon_aaraj has joined #river
mon_aaraj has quit [Ping timeout: 268 seconds]
mon_aaraj has joined #river
Nulo has quit [Ping timeout: 268 seconds]
mon_aaraj has quit [Ping timeout: 256 seconds]
mon_aaraj has joined #river
snakedye has quit [Ping timeout: 240 seconds]
waleee has quit [Ping timeout: 240 seconds]
snakedye has joined #river
Nulo has joined #river
Nulo has quit [Read error: Connection reset by peer]
Nulo has joined #river
snakedye has quit [Ping timeout: 256 seconds]
mon_aaraj has quit [Ping timeout: 240 seconds]
mon_aaraj has joined #river
<ifreund> mon_aaraj: actually was a river issue, pushed a fix :)
snakedye has joined #river
<novakane> that kinda weird that it makes multiple request for set_anchor
mon_aaraj has quit [Ping timeout: 268 seconds]
mon_aaraj has joined #river
mon_aaraj has quit [Ping timeout: 250 seconds]
mon_aaraj has joined #river
snakedye has quit [Ping timeout: 250 seconds]
mon_aaraj has quit [Ping timeout: 240 seconds]
mon_aaraj has joined #river
waleee has joined #river
waleee has quit [Ping timeout: 240 seconds]
waleee has joined #river
waleee has quit [Ping timeout: 256 seconds]
mon_aaraj has quit [Ping timeout: 250 seconds]
mon_aaraj has joined #river
<Snektron[m]> Hello, i have a dual monitor setup and previously used kanshi to configure my outputs. Recently though i started having some problems with it: when i start it as a service or on my secondary monitor, river (or wlroots) crashes
<Snektron[m]> It works fine on my primary monitor though
<Snektron[m]> im not sure exactly at what point in the log the crash happens
mon_aaraj has quit [Ping timeout: 240 seconds]
mon_aaraj has joined #river
<Snektron[m]> Ah, it crashes around like 293
<Snektron[m]> It doesn't seem like this contains a lot of useful information, and kanshi doesn't output anything interesting either. Does anyone know how i can look into this further?
<novakane> that log kinda looks like https://github.com/riverwm/river/issues/508
<novakane> even totally looks like it
<ifreund> Snektron[m]: yeah, that's #508. I left a possible fix in the comments but I'm pretty sure it's just a workaround and the real issue is a wlroots 0.15 regression
<ifreund> feel free to apply the patch and let me know if you see any strange behavior: https://github.com/riverwm/river/issues/508#issuecomment-1016852268
<ifreund> it should fix the crash, but I think it will also cause output configuration to not be fully applied
<ifreund> I need to find time to dig into the wlroots output code...
gwizon has quit [Quit: Lost terminal]
<mon_aaraj> ifreund: Yeah, I've just seen it on the issue! Thank you so very much for helping
<mon_aaraj> I'll just be testing the new patch and I'll close the issue when I confirm it is working on my machine
elshize has quit [Ping timeout: 240 seconds]
elshize has joined #river
waleee has joined #river
<Snektron[m]> ifreund: thanks. I tried the patch and indeed it doesn't cause the configuration to be applied
<Snektron[m]> the weird part is how it only crashed when launched from a terminal on the secondary monitor
<Snektron[m]> how does that even work
mon_aaraj has quit [Ping timeout: 240 seconds]
mon_aaraj has joined #river
<ifreund> Snektron[m]: I think that's irrelevant, if I understand correctly it's a race condition with the rendering loop
<Snektron[m]> feels like something like that. For now i'll just launch kanshi manually
mon_aaraj has quit [Ping timeout: 268 seconds]
mon_aaraj has joined #river
snakedye has joined #river