00:34 <Gozenka> One more:

00:34 <Gozenka> Popup "Changes you have made may not be saved" when trying to close a tab on Chromium does not get displayed, seemingly locking up input. Spawn a new window, and it shows up in front of Chromium in the proper place.

00:34 <Gozenka> Might be happening on all popups.

00:37 <Gozenka> "Save as" opens up as a tiled window, rather than floating. I could not think of another popup window to test this.

09:52 <stefur> Hi! I'm on river 0.3.0-dev.95+e4e8eae trying out the new rules system and noticed that borders are no longer drawn for some specific applications, such as Firefox, Thunderbird and pcmanfm. I'm guessing I might be missing something here? Any help appreciated!

09:57 <ifreund> stefur: river will now default to CSD if the client does not support xdg-decoration

09:58 <ifreund> you can restore the old behavior of forcing SSD everywhere with `riverctl rule-add ssd`

10:02 <stefur> Ah I see, that worked great. Thank you!

10:02 <ifreund> no problem!

10:36 <kotto> Ok, after some sleep I now can get the focused and urgent tags. But I'm not sure how to deal with the view_tags as it is anyopaque. Should I cast that to something?

10:45 <ifreund> kotto: you can use view_tags.slice(u32), https://github.com/ifreund/zig-wayland/blob/e9484c814801b520cbe4ed719cceb4d0a59f1341/src/common_core.zig#L35

10:46 <ifreund> once my upstream wayland MR gets merged zig-wayland can just generate slice arguments directly: https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/300

11:17 <kotto> thanks, That helped a lot!

14:17 <Gozenka> Update: It is not related to the initial state. Crash happens whenever a new monitor is enabled and focus switches to it.

14:17 <Gozenka> Abortedfailed to dispatch wayland eventsonnector eDP-1: Modesetting with 1920x1080 @ 60.008 Hz Hzaphics 630 (KBL GT2)for daily use

14:18 <Gozenka> This is the message I get.

14:18 <Gozenka> If you like I can try to get a log

14:31 <Gozenka> https://0x0.st/HiUS.log

14:32 <upsala> I have a weird issue. Sometimes (I haven't quite figured out when yet) my super key isn't recognized as the super key anymore by river. When I run 'xev' it still is called SUPER_L but when I press 'Super+d' (which is my bind for rofi) it behaves as pressing 0, which locks nnn. Ctrl, Alt, Shift behave as they should but Super just stops working. Restarting river fixes this. Any ideas what this could be?

14:34 <Gozenka> Without Vulkan: https://0x0.st/HiU1.log

14:39 <Gozenka> - Start with two monitors

14:39 <Gozenka> - wlr-randr --output eDP-1 --off

14:39 <Gozenka> - wlr-randr --output eDP-1 --on

14:39 <Gozenka> - switch focus to eDP-1 and spawn window

14:39 <Gozenka> - crash

14:40 <Gozenka> sometimes crashes even before spawning window

14:43 <ifreund> Gozenka: yeah there's a race condition with the transaction system and creating/destroying outputs I haven't been able to reproduce the crash but I've gotten some funky behavior

14:43 <ifreund> if you manage to get a stack trace with a debug build from the crash that might be helpful, that log you sent is already useful though

14:44 <Gozenka> I used the debug build and the loglevel command to start river as in the wiki. Is there anything else I can do?

14:45 <ifreund> ah I guess that log does have a stacktrace just formatted a bit differently for some reason

14:46 <ifreund> I think I have enough to go on for now, I'll open an issue

14:46 <Gozenka> ok, good luck :)

14:51 <ifreund> upsala: is there a chance you ran a "riverctl enter-mode foo" command by accident? I think there's one in the example init that has confused people before

14:51 <ifreund> other than that I have no idea what it could be unfortunately

14:51 <Gozenka> Another small one: Cursor does not warp to other monitor if both monitors have zero windows showing at that moment. If either one has a window, it warps.

14:52 <Gozenka> with: riverctl set-cursor-warp on-output-change

14:54 <ifreund> Gozenka: would you mind opening an issue for that one so I don't forget to come back to it?

14:54 <ifreund> going to prioritize the crash

14:54 <Gozenka> sure

14:54 <upsala> That could actually be it, thanks

14:55 <ifreund> no problem!

15:07 <upsala> I think I have to put that somewhere else, it's too close to other used binds on my split keyboard

16:14 <upsala> Did anything major change in the last 2 days with resizing of windows? When I resize a floating mpv view now and drag up the bottom border, the aspect ratio of the video stays the same but the view border is now inside the video

16:15 <ifreund> upsala: what changed there is that we no longer tell mpv that it is "tiled" while it is actually floating

16:15 <upsala> A couple of days ago it would change the video size and put black chunks on the left/right of the video to compensate

16:15 <ifreund> I agree that the current behavior is weird, river should draw the borders at the size the client actually takes rather than the size requested by river

16:16 <upsala> Ah I see

16:17 <ifreund> Feel free to open an issue on github so I don't forget about it :)

16:17 <upsala> Would the text I just wrote suffice for the issue?

16:17 <upsala> Or should I add an image or something

16:52 <leon-p> not just border, but also use the clients actual buffer size as view size, I think. Those getting out of sync was a pretty annoying thing in pre-scene river

18:30 <upsala> I created an issue, I hope this is explained well enough

19:29 <p00f1> ifreund: just fyi, the css patch removes the headerbar even where it's needed, like here : https://imgur.com/cfhg3ma

19:31 <p00f1> the gtk patch does the correct thing

19:31 <p00f1> s/css patch/css snippet

19:36 <Gozenka> That should be obvious, but a warning might be good :)

19:36 <Gozenka> I preferred such a way and shared it here, because I know I will never need CSD with my applications, and I prefer to keep as much as possible on my system as defaults from the package manager to keep it simple, except for some specific programs I am intent on following the latest versions of and customizing via their git versions.

19:37 <p00f1> yeah now that i think about it, it is obvious lol

21:01 <jacobly> what are the default config colors so that I can properly reset them?

21:04 <jacobly> figured it out