03:04 <leon-p> ifreund: sweet!

03:25 <IchikaZou> Will river add support to swaylock-effects? When I run it, river say it’s not supported.

07:30 <Guest261203> Hey, apologies for the trouble but I am having a tiny issue, I'm absolutely loving river so far but for some reason native wayland GUI applications are opened with a title bar that I can't seem to get rid of, I've tested by installing sway and running them from there and the problem goes away, meanwhile if I run them through xwayland in River the

07:30 <Guest261203> bar also goes away, I wanted to know if there was a way to fix it because I've been searching for a long time already on how to fix it but couldn't find anything.

07:35 <novakane> Guest261203: see this https://github.com/riverwm/river/wiki#how-do-i-disable-gtk-decorations-eg-title-bar

07:43 <Guest261203> novakane: I can't believe I missed something so obvious, checked beforehand the issues section but didn't see that one, unfortunately I'm still seeing the bar on applications like my pdf reader, is there another command apart from "gsettings set org.gnome.desktop.wm.preferences button-layout """ that could help with it?

07:43 <Guest261203> Regardless, thank you for your help, I really appreciate it

07:46 <novakane> nope, that need to be done on gtk side

07:48 <Guest261203> novakane: You mean by configuring gtk itself? I did try that but didn't have much luck, although my browser having no tab anymore is definitely a start so I'll try again and see what I can find

07:49 <novakane> Guest261203: no I mean by patching gtk, iirc ifreund shared one once

07:50 <Guest261203> novakane: Oh, is the patch anywhere on github?

07:50 <Guest261203> Nevermind, think I found it

07:52 <Guest261203> My only problem is gonna be figuring out where to apply this patch

08:00 <novakane> probably to the gtk source code and building it

08:00 <novakane> or maybe it could be applied to your distro package if it can use patch

08:00 <Guest261203> Maybe, I'm downloading the src right now, gonna try my luck with it

08:03 <Guest261203> Strange

08:03 <Guest261203> novakane: The patch made by the developer seems to be targetting a file that doesn't exist within the gtk source code

08:03 <Guest261203> "gdk-private.c"

08:04 <Guest261203> Already tried searching recursively for the file with find

08:10 <novakane> is that what you used ? https://libera.irclog.whitequark.org/river/2023-02-22#33872160;

08:11 <Guest261203> novakane: Ohhh, I downloaded the patch from the gtk merge request, my apologies and thank you, gonna try it out now

08:12 <novakane> ah yeah, the merge requested is not completed and abandoned so yeah it probably doesn't work

08:16 <Guest261203> Welp, time to wait for the thing to compile

08:20 <novakane> yeah that why I will never try this patch lol

08:48 <Guest40123> Welp, can't tell if I patched completely wrong but seems like it didn't work

08:55 <Guest40123> Eh I give up for now, only thing it's affecting is my pdf reader and even then going fullscreen removes the bar so

09:02 <angry_vincent> patch works for me

09:56 <hush> Hi there. Hope you can help me out with one little problem which btw I think it's related more to wayland rathern than river, but since river it's now my only wm of choice I'd like to fix it here. So: window borders, or 'the text inside tabs'. Its size doesn't change whatever zoom setting I set in the browser, and some application don't even have a zoom setting (or if they have it it doesn't work

09:56 <hush> anyway). Is there a way like in Sway via .Xdefaults or in Gnome via 'font settings' to set a magnification level for ALL fonts?

09:57 <hush> I thought that .Xdefaults was the wayland-way but apparently it doesn't work in river v0v

13:49 <boombim> hello. does river have a hook before it will be closed?

14:11 <tleydxdy[m]> I assume you close river via a keybind?

20:35 <IchikaZou> I encounter a weird situation that swaylock work on river but swaylock-effects doesn’t work, anyone use swaylock-effects experience this problem?

20:36 <ifreund> IchikaZou: probably swaylock-effects doesn't support ext-session-lock

20:36 <ifreund> they should probably rebase on upstream swaylock

20:37 <ifreund> river doesn't support the old insecure ways of screenlocking any more

20:38 <IchikaZou> Current swaylock-effects seem to have ext-session-lock supported since it can be use on newest sway releases.

20:39 <ifreund> what error do you get?

20:41 <IchikaZou> compositer does not support the input inhibitor protocol, refusing to run insecurely

20:42 <ifreund> IchikaZou: it's not using ext-session-lock then

20:42 <ifreund> ext-session-lock doesn't require the input inhibitor protocol

20:43 <IchikaZou> I see, I will file a bug report to swaylock upstream

20:43 <ifreund> IchikaZou: no, to swaylock-effects

20:43 <IchikaZou> swaylock-effects upstream

20:43 <IchikaZou> Sorry

20:43 <ifreund> no worries!

22:47 <rodrgz> IchikaZou: I'm using swaylock-effects, even on river with scene graph, it works fine...

22:52 <rodrgz> Very smooth experience with scene graph. River was good, now it's better. The only "problem" so far was the size of the cursor that diverges over a window and over the background/wallpaper.