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/
elshize has quit [Ping timeout: 240 seconds]
elshize has joined #river
vaivis has quit [Read error: Connection reset by peer]
lxsameer has quit [Ping timeout: 272 seconds]
notzmv has quit [Ping timeout: 250 seconds]
waleee has quit [Ping timeout: 248 seconds]
snakedye has joined #river
vaivis has joined #river
notzmv has joined #river
groknull has joined #river
groknull has quit [Remote host closed the connection]
<novakane> NickH: what's your river version?
<novakane> and also do you have wayland 1.20?
vaivis has quit [Read error: Connection reset by peer]
<novakane> leon-p: latest commits on your waylock PR https://0x0.st/oAPx.png https://0x0.st/oAP3.png https://0x0.st/oAPY.png
<leon-p> NickH: works for me. I am always on the latest river release and develop all my softwarr against that.
<leon-p> novakane: thanks. That's really weird, there rrally should be no gradient there
<novakane> it would make more sense if the gradient were like blue to red
<novakane> from one of the 3 colors to another one
snakedye has quit [Ping timeout: 248 seconds]
<leon-p> there just shouldn't be a gradient at all. The viewport source never contains more than a single pixel.
<novakane> weird, really no idea why
lxsameer has joined #river
talismanick has quit [Ping timeout: 250 seconds]
pkap has joined #river
waleee has joined #river
snakedye has joined #river
notzmv has quit [Ping timeout: 260 seconds]
<leon-p> I might have to switch to three 1px buffers instead of 1 3px buffers.
vaivis has joined #river
vaivis has quit [Read error: Connection reset by peer]
vaivis has joined #river
vaivis has quit [Read error: Connection reset by peer]
snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
vaivis has joined #river
vaivis has quit [Read error: Connection reset by peer]
notzmv has joined #river
chipps__ has quit [Ping timeout: 260 seconds]
<NickH> river 0.1.3 and wayland 1.20.0
<NickH> Also for river built from head on April 23rd
<ifreund> NickH: what does `wayland-info` print when you run it under your river instance where lswt doesn't work?
<ifreund> It's probably part of a wayland-utils package
<NickH> Could be something about my river build though... I'm making a deb package and then installing that. I'll check with a standard river build tomorrow.
<NickH> Hmm... don't know about wayland-utils
<NickH> % wayland-info
<NickH> zsh: command not found: wayland-info
<NickH> What provides 'wayland-info'?
<NickH> Used the canonical search for files within Debian and nothing was returned.
<NickH> "apt-file search wayland-info"
<novakane> search for wayland-utils as mentionned above
<NickH> My wayland install is from the debian package.
<mizzunet> Is there way to set `xkb_numlock enable` on river?
<NickH> Search how?
<NickH> locate? find? apt-cache search? apt-file search?
<novakane> in the distro packages
<tiosgz`> NickH: from what i can see it's not packaged on debian
<NickH> tiogz: that would explain why I can't find it.
<NickH> I've not dug into the Debian wayland packages. I don't know why it would have been excluded.
<NickH> I'll try to look into it. But not now... it's Saturday night here, I'm a few glasses in, and the missus is wondering why I'm still at my desk ;-)
<novakane> mizzunet: I don't think so
vaivis has joined #river
vaivis has quit [Read error: Connection reset by peer]
<leon-p> ifreund: not sure if you've read the messages, but I think the 3px buffer approach for waylock doesn't work correctly because of server-side rounding issues. So I think we'll need three distinct 1px buffers
<mizzunet> oh
vaivis has joined #river
<ifreund> leon-p: fine by me, we can have 3 wl_buffers that share a common 3px backing memory
<pkap> ifreund: How do you feel about clearing with ctrl-u in waylock?
<ifreund> pkap: planning on implementing that, just haven't gotten around to it yet
<ifreund> it's by far the most common feature request :D
<pkap> Ok cool I make a PR for that
<ifreund> pkap: sure, go for it
<novakane> ifreund: you want to keep the quiet option of wget or I just close the PR?
<novakane> I find way too noisy but as youu want
<ifreund> novakane: does it still print error messages with the quiet option?
<novakane> not sure, let me make some test
<novakane> hmm looks like it doesn't, I just close the PR
vaivis has quit [Read error: Connection reset by peer]
vaivis has joined #river
pkap has quit [Quit: Ping timeout (120 seconds)]
elshize has quit [Ping timeout: 246 seconds]
elshize has joined #river
<leon-p> btw, do we consider those rounding issues a bug?
<ifreund> leon-p: maybe, not sure. If so then it would be a wlroots bug I'm pretty sure
<ifreund> could also just be wl_fixed being trash as usual though
<tiosgz`> leon-p: with 7d612b1: wl_display@1.error(nil, 1, "invalid width, height or stride (1x1, 12)")
<tiosgz`> i think the `height` and `width` variables are rather misleading now (& the source of the error)
<leon-p> tiosgz`: thanks, although I finally managed to get a working river with session lock, so I can test myself now :D
vaivis has quit [Read error: Connection reset by peer]
vaivis has joined #river
snakedye has quit [Ping timeout: 250 seconds]
snakedye has joined #river
elshize has quit [Ping timeout: 276 seconds]
snakedye has quit [Ping timeout: 250 seconds]
elshize has joined #river
snakedye has joined #river
elshize has quit [Ping timeout: 240 seconds]
elshize has joined #river
vaivis has quit [Read error: Connection reset by peer]
snakedye has quit [Ping timeout: 250 seconds]
snakedye has joined #river
notzmv has quit [Ping timeout: 248 seconds]
talismanick has joined #river
notzmv has joined #river
lxsameer has quit [Ping timeout: 240 seconds]
<NickH> So it seems wayland-utils is not actually a part of wayland. So it's not that it was excluded from the wayland build, but just that no one has packaged it.
<leon-p> NickH: it used to be a weston test client before it got split into its own thing
<NickH> wayland-info output is at https://0x0.st/oAcb.out