13:12 <agz> how much stable is river rn compared to hyprland

13:14 <sewn> yes

13:14 <ifreund> agz: I've never used hyprland so I can't comment too much there but river has very few known bugs

13:15 <ifreund> if you're asking about breakng changes requiring users to modify their configuration, river is not yet stable in that sense and won't be for a couple years still most likely

16:25 <The_Buhs> agz: it's felt about the same to me in terms of stability wrt breaking changes. My config hasn't really had to change with river updates (so far, I know the wm protocol will be some big changes), but actually updating can be more of a hassle since zig is still relatively niche depending on the distro you use.

16:50 <LarstiQ> there was some incompatibility between 0.2 and 0.3, but none too bad imo

17:42 <agz> hi, so i was thinking of playing around with river a bit, can i use it inside a vm with arch ?

17:50 <leon-p> you can also just run it nested inside your current desktop

18:46 <sewn> I've been told wlr layer surface configure being called three times in a row before wl surface enter is called is a river bug

19:04 <leon-p> we'll need more information on that, like f.e. a full WAYLAND_DEBUG log

19:04 <leon-p> also AFAIK a server can call configure whenever it pleases. It may not be very elegant, but it should still be legal, no?

19:09 <sewn> leon-p: https://0x0.st/Xafr.txt

19:11 <leon-p> what's the client?

19:15 <sewn> are you asking for source code?

19:16 <leon-p> perhaps

19:16 <leon-p> also for context what it's actually wanting to achieve

19:17 <sewn> its grabbing a frame of the screen and then displaying it using a layer surface

19:17 <leon-p> I see

19:17 <sewn> https://codeberg.org/sewn/wfreeze/raw/branch/master/wfreeze.c

19:18 <leon-p> is it having any actual issues? because any client really should be able to handle a few configure events...

19:19 <sewn> yes but it is concerning its being sent three times in a row

19:19 <sewn> ive asked about it in #wlroots but told it was a bug in river

19:19 <leon-p> it very well may be, HOWEVER a client that can't handle two extre configure events is also buggy 🤷

19:20 <sewn> okay..

19:25 <leon-p> your event loop seems really weird to me, what exactly is the purpose of this program?

19:26 <leon-p> a wayland client really shouldn't just stop dispatching

19:32 <leon-p> on *BSD you could use kqueue, on linux pidfd and poll to combine your wayland event dispatching with waiting for the child to exit

19:33 <leon-p> because if you stop dispatching, bad things happen

20:35 <husk9> hi, setting up obs screen capture for the first time. i'm failing on the last 8th point of the "It doesn't work" Troubleshooting Checklist (https://github.com/emersion/xdg-desktop-portal-wlr/wiki/%22It-doesn't-work%22-Troubleshooting-Checklist)

20:37 <husk9> looking at the output of `pw-dump | jq`, all my .params.Format keys hold empty lists, e.g. "Format": []

20:39 <husk9> in obs i can add Pipewire-specific sources, but they are all broken. for instance, "Screen Capture (PipeWire)" periodically asks me to select a screen (my cursor changes, presumably to click on the screen), but clicking changes the cursor back and doesn't do anything

20:40 <husk9> on standard output i see "info: [pipewire] Asking for desktop" and "warning: [pipewire] Failed to start screencast, denied or cancelled by user"

20:42 <husk9> i am on Arch running the latest packages: kernel 6.9.7, PipeWire 1.2.0 + Wireplumber 0.5.0, River 0.3.0, xdg-desktop-portal 1.18.4, xdg-desktop-portal-wlr 0.7.0

20:43 <husk9> not sure where to proceed next. would be thankful for any pointers

20:45 <husk9> oh, i forgot to mention the most important thing. i have an NVIDIA GeForce 1060 with the 555.58 proprietary driver

20:49 <vyivel> iirc nvidia works with a different format

20:49 <vyivel> nvidia proprietary driver*

20:53 <husk9> tbh the 8th instruction is not very clear to me, so i don't know what the expected value for Format should be

20:57 <vyivel> just check if it exists afaiu

20:58 <husk9> well, the key "exists", but the values are empty lists as mentioned. not sure if that counts