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/
waleee has quit [Ping timeout: 248 seconds]
eShaev9z_ has joined #river
eShaev9z has quit [Ping timeout: 256 seconds]
jao has quit [Ping timeout: 246 seconds]
leopoldek has quit [Ping timeout: 248 seconds]
Nosrep has quit [Ping timeout: 250 seconds]
Nosrep has joined #river
Guest78K has joined #river
Guest78K has quit [Quit: Client closed]
kotto has joined #river
uncomfy has joined #river
Szadek45 has joined #river
Szadek4 has quit [Ping timeout: 240 seconds]
Szadek45 is now known as Szadek4
leopoldek has joined #river
kotto has quit [Quit: WeeChat 4.0.3]
<daurnimator> ifreund: out of curiousity, are you expecting to do a 0.11 compatible release soon?
<leon-p> daurnimator: I think the plan is to do one last release for 0.10 and then a point-release for 0.11
<leon-p> release is currently blocked by a few bugs and by redesigning how resizes work
<daurnimator> for Arch we're likely to bump Zig to 0.11 shortly which result in an inability to build the current (and any non-0.11 compatible) releases.
<ifreund> hmm, there hasn't been a wlroots release since river 0.2.4 so it probably wouldn't be too annoying to do a 0.2.5 for zig 0.11 if that's somethng distros need
<ifreund> I can't give a good estimate on when 0.3.0 will land, as leon-p said there are multiple blocker currently but I'm about to have a lot more free time
<ifreund> a month or so might be realistic
<ifreund> not totally sure if I want to make 0.3.0 compatible with zig 0.10 or go straight to 0.11
notzmv has quit [Ping timeout: 246 seconds]
uncomfy has quit [Remote host closed the connection]
chraist has joined #river
chraist has quit [Quit: Leaving]
lbia has joined #river
lbia1 has joined #river
lbia has quit [Quit: lbia]
jao has joined #river
jao has quit [Ping timeout: 246 seconds]
<Nosrep> logs from firefox crash https://0x0.st/H9se.txt
lbia1 has quit [Quit: lbia1]
<Nosrep> caused by dragging a tab (up(?))
<Nosrep> i don't have any river or the whole output unfortunately
lbia has joined #river
<ifreund> Nosrep: that's 100% a bug in firefox or maybe gtk, it's passed NULL as the "origin" argument of the start_drag request which is a violation of the protocol
waleee has joined #river
Guest78K has joined #river
<Nosrep> fun
<Nosrep> there's gotta be a bug on bugzilla already right
Guest78K has quit [Quit: Client closed]
<Nosrep> found one but it's for a drawing tablet and is fixed, the other drag ones aren't exactly similar i think
jao has joined #river
<ifreund> passing something that can apparently return NULL due to a race or something directly to start_drag() is a bug
<Nosrep> love race conditions, so fun
<Nosrep> is there anything for the bug already or nah
<ifreund> I didn't see any issue from a quick search
<ifreund> I'm also not sure if it's still present in gtk4 or not, firefox uses gtk3 still
jmcantrell has joined #river