ChanServ changed the topic of #river to: river - a dynamic tiling Wayland compositor || https://codeberg.org/river/river || channel logs: https://libera.irclog.whitequark.org/river/
notzmv has quit [Remote host closed the connection]
glenneth has quit [Ping timeout: 255 seconds]
glenneth- has joined #river
Palanix_ has joined #river
Palanix has quit [Ping timeout: 265 seconds]
Palanix_ is now known as Palanix
eShaev9z has quit [Ping timeout: 272 seconds]
eShaev9z has joined #river
glenneth- has quit [Changing host]
glenneth- has joined #river
glenneth- is now known as glenneth
<Nickli> ran across a combined notification manager and bar yesterday https://github.com/Aylur/ags
<Nickli> not sure if it does notifications themselves too
aryak has quit [Ping timeout: 252 seconds]
aktina has quit [Ping timeout: 252 seconds]
basrandir has quit [Remote host closed the connection]
fitrh has joined #river
fitrh has quit [Remote host closed the connection]
aryak has joined #river
aktina has joined #river
catman has quit [Quit: WeeChat 4.4.2]
catman has joined #river
leopoldek has joined #river
haliucinas has quit [Read error: Connection reset by peer]
haliucinas1 has joined #river
leopoldek has quit [Remote host closed the connection]
<__toor__> it seems to depend on every kind of technology under the sun though... that might be a problem for me.
<The_Buhs> __toor__ the joys of lfs :)
<Nickli> __toor__, which one?
leopoldek has joined #river
Guest1 has joined #river
Guest1 has quit [Client Quit]
<leon-p> huh, seems like there is a new notification spec, this time with portals. I wonder if this will finally allow per-session notifications
<Nickli> now you'r thinking with portals
<leon-p> i see what you did there
tiosgz has joined #river
<tiosgz> i've just found my logs are spammed with "debug(wlroots): [types/output/output.c:563] Primary buffer size mismatch" (70k out of 80k lines)
<tiosgz> i don't have much time to look into it rn, but is it happening to anyone else?
<tiosgz> (apparently this may have something to do with fullscreened stuff, but i only ever full-screen something by accident and definitely didn't fullscreen anything last session, at least not for that long?)
<tiosgz> (oh, but screen lock also counts as sort-of fullscreen [wrt attempting direct scan-out] which explains a lot)
<tiosgz> and i have something like 1.25 output scale which probably explains this
<tiosgz> but still i'd prefer to avoid the messages so prolly i have to look into it
<ifreund> tiosgz: reminds me of https://codeberg.org/river/river/issues/816
<ifreund> could be unrelated though
<tiosgz> ah, thanks! i don't see the row/column of random pixels but apparently it's getting 1706*1.125 = 1919.25 which is off (1706 is the surface size seen in a wayland debug log, 1920 screen width)
tiosgz has quit [Quit: nyaa~]
<__toor__> Nickli: Aylur/ags - vala, npm, javascript, golang, that's what I remember at least
<__toor__> the list of stuff needed to compile a bar + notification daemon seemed a bit overkill
leopoldek has quit [Ping timeout: 264 seconds]
jetpackjackson has joined #river
angle is now known as ang1e
ang1e has quit [Remote host closed the connection]
ang1e has joined #river