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/
mtm has quit [Ping timeout: 248 seconds]
mtm has joined #river
catman has joined #river
sespiros has quit [Quit: ZNC 1.9.1 - https://znc.in]
sespiros has joined #river
Guest18 has joined #river
mx08 has quit [Quit: WeeChat 3.8]
mx08 has joined #river
elshize has quit [Ping timeout: 246 seconds]
Guest18 has quit [Ping timeout: 256 seconds]
Guest18 has joined #river
palanix_ has joined #river
Snetry has quit [Ping timeout: 252 seconds]
palanix has quit [Ping timeout: 272 seconds]
palanix_ is now known as palanix
Snetry has joined #river
Guest18 has quit [Ping timeout: 256 seconds]
seb_ has joined #river
seb_ has quit [Client Quit]
fitrh has joined #river
fitrh has quit [Quit: fitrh]
fitrh has joined #river
fitrh_ has joined #river
fitrh has quit [Read error: Connection reset by peer]
aryak has quit [Remote host closed the connection]
aktina has quit [Remote host closed the connection]
sewn has quit [Remote host closed the connection]
aktina has joined #river
aryak has joined #river
sewn has joined #river
pingutz has joined #river
<pingutz> hi, is there a reason why I can move firefox around in floating mode with the mouse  but nothing else?
<pingutz> tried a quick google but didn't find anything
pingutz has quit [Client Quit]
pingutz has joined #river
pingutz has quit [Client Quit]
fitrh has joined #river
fitrh_ has quit [Ping timeout: 252 seconds]
bitblt has joined #river
<bitblt> Hello! Is there something like hyprland's xwayland:force_zero_scaling (https://wiki.hyprland.org/Configuring/XWayland/#hidpi-xwayland) in river?
<ifreund> nope
<bitblt> are there any plans for similar functionality?
<ifreund> bitblt: I'd rather see proper Xwayland scaling support than a bandaid workaround
<ifreund> It's not something I'm personally working on right now though
<bitblt> isn't this: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1197 a step to the right direction?
<ifreund> probably, though I don't know how much of the related code is shared between rootless and rootful Xwayland
<ifreund> (rootful is running Xwayland + an X window manager in its own "window" under a wayland compositor)
<ifreund> rootful doesn't require the wayland compositor to do anything, it behaves just like a normal wayland client
<ifreund> rootless Xwayland is how individual X11 client integrate into your native wayland copositor/window management
<ifreund> and requires quite extensive support in the compositor
<bitblt> ah i see
notzmv has quit [Ping timeout: 248 seconds]
fitrh_ has joined #river
fitrh has quit [Ping timeout: 265 seconds]
notzmv has joined #river
mtm has quit [Ping timeout: 276 seconds]
mtm has joined #river
elshize has joined #river
fitrh_ has quit [Read error: Connection reset by peer]
legoraft has joined #river
legoraft has quit [Remote host closed the connection]
legoraft has joined #river
legoraft has quit [Ping timeout: 272 seconds]
legoraft has joined #river
legoraft has quit [Remote host closed the connection]
notzmv has quit [Read error: Connection reset by peer]
legoraft has joined #river
legoraft has quit [Remote host closed the connection]
legoraft has joined #river
legoraft has quit [Remote host closed the connection]
legoraft has joined #river
fitrh has joined #river
legoraft has quit [Ping timeout: 245 seconds]
notzmv has joined #river
legoraft has joined #river
fitrh has quit [Quit: fitrh]
legoraft has quit [Ping timeout: 252 seconds]
Guest59 has joined #river
Guest59 has quit [Client Quit]
legoraft has joined #river
elshize has quit [Ping timeout: 276 seconds]
legoraft has quit [Ping timeout: 255 seconds]
elshize has joined #river
legoraft has joined #river
legoraft has quit [Remote host closed the connection]
proycon has quit [Ping timeout: 252 seconds]
proycon has joined #river
proycon has quit [Remote host closed the connection]
siaal has quit [Quit: ZNC - https://znc.in]
siaal has joined #river
proycon has joined #river
talisman` has quit [Remote host closed the connection]
Guest69 has joined #river
<Guest69> Hey, I've tried both wideriver and rivertile and they both seem to open the new window as the new master. Is there a way to make it instead appear in 'slave' area?
<ifreund> Guest69: you are probably looking for riverctl attach-mode ...
<Guest69> Thanks that was it!
<Guest69> Also I feel really dumb, but isn't there any keybind to resize tiled windows? is it just by in/de-creasing the main stack area?
<TheAnachron> Guest69: did you read the manual of those layout managers? It reall depends on the implementation
Guest64 has joined #river
<Guest69> yeah I did, all they have is to increase/decrease the main area size, but can't really resize individual windows
<TheAnachron> Yep then that's it. How would that work?
<Guest69> Not sure? I'm just used from the others WMs I've been using, awm/hyprland/sway/gnome-paperwm/kde-karousel that you can always resize the individual windows
<Guest69> another issue I'm having is that when working I love to move some floating windows a little bit to the edge of the screen, so part of the window is invisible and I can work on the window below it - but with river it seems like you can't move the windows out of the view and they are clipped to the screen? is there some toggle for that?
<TheAnachron> Guest69 I mean how do you expect that function to work? Will the window "jump" out of the stack, or the stack is adjusted (other windows around it are getting smaller/bigger) or how does that work? I never used either of those
<Guest69> Yeah, other windows around it are getting smaller/bigger, but I guess this is not how river is supposed to work.
<TheAnachron> Honestly this is not about river but more how the layout generator is working.
<TheAnachron> The default one iirc cannot do that, but maybe some of the others can
<TheAnachron> I just havent used any of them, so I am hoping someone else here has and can answer your question positively
<Guest69> What about this?
<Guest69> "another issue I'm having is that when working I love to move some floating windows a little bit to the edge of the screen, so part of the window is invisible and I can work on the window below it - but with river it seems like you can't move the windows out of the view and they are clipped to the screen? is there some toggle for that?"
<Guest69> I can't be the only one annoyed by it? in pretty much any other wm/de/os you can move the window so parts of it is "outside" the monitor area
<TheAnachron> Never wanted that. I either have my windows tiled, so they are all completely visible, or I make them floating and I can put them wherever I want.
<Guest69> ):
<Guest69> Thanks for the help!
emersion has quit [Remote host closed the connection]
emersion has joined #river
Guest69 has quit [Quit: Client closed]
Guest64 has quit [Quit: Client closed]
Guest91 has joined #river
<Guest91> Hi! Could anyone help me fix the SCREEN SHARING on my system? I would be forever grateful. When I used Hyprland, it worked. I don't know if they do anything different with "xdg-desktop-portal-hyprland".
<Guest91> When I try to test it using https://mozilla.github.io/webrtc-landing/gum_test.html I get:
<Guest91> NotAllowedError: The request is not allowed by the user agent or the platform in the current context.
<Guest91> ---
<Guest91> Before you ask:
<Guest91> My user is a member of the "video" group.
<Guest91> Services "dbus" and "seatd" are enabled and started.
<Guest91> I have the "XDG_RUNTIME_DIR" created at "/var/run/user/`id -u`" (as it should be for FreeBSD) with 700 permissions.
<Guest91> Upon starting River, I checked that "WAYLAND_DISPLAY" gets properly set to "wayland-1". Other variables I set are:
<Guest91> export MOZ_ENABLE_WAYLAND=1
<Guest91> export XDG_CURRENT_DESKTOP=river
<Guest91> export XDG_RUNTIME_DIR=/var/run/user/`id -u`
<Guest91> export XDG_SESSION_TYPE=wayland
<Guest91> Interesting that even though I export "XDG_CURRENT_DESKTOP", by the time all files are sourced, its value is empty string...
<Guest91> I tried starting River using just the `river` binary as well as using `dbus-run-session -- sh -c "river"`. Neither way gets me to share screen.
<Guest91> In River's init file, I use `riverctl spawn` to start "pipewire" and "wireplumber". I tried not starting them, and that obviously does not help either.
<Guest91> I reviewed anything I could get my hands online such as the article below but
<Guest91> nothing helped:
<Guest91> ---
<Guest91> System information:
<Guest91> Operating system is FreeBSD 14.1-RELEASE-p5.
<Guest91> These relevant packages are installed listed below.
<Guest91> river-0.3.5
<Guest91> wayland-1.23.1
<Guest91> wayland-protocols-1.38
<Guest91> xwayland-24.1.4,1
<Guest91> xdg-desktop-portal-1.18.4
<Guest91> xdg-desktop-portal-gtk-1.15.1_1
<Guest91> xdg-desktop-portal-wlr-0.7.1
<Guest91> dbus-1.14.10_5,1
<Guest91> seatd-0.9.1
<Guest91> pipewire-1.2.6_4
<Guest91> wireplumber-0.5.6_1
<Guest91> I tried removing "xdg-desktop-portal-gtk" but it does not make any difference.
<TheAnachron> Guest91: are you sure xdg-desktop-portal-wlr is the only portal running?
<Guest91> TheAnachron When I run `ps aux | grep xdg-desktop-portal` I only get ` /usr/local/libexec/xdg-desktop-portal`
Guest72 has joined #river
<Guest72> Hey quick question, i have problems with my stylus
<Guest72> I want it to be usable as a mouse, like for example in sway, but after enabling every input device there still is nothing showing up in wev
<Guest72> One input device is named tablet_*_stylus btw and it works in xournalpp
<TheAnachron> Guest91 have you checked https://wiki.archlinux.org/title/XDG_Desktop_Portal ?
<Guest91> TheAnachron: Do you have XDG_CURRENT_DESKTOP=river? Also from Section 4.1 in your AW article, I cannot run sysctl command as FreeBSD does not use systemd? How do you use dbus in all this? Do you just enable the service or do you do anything specific with dbus?
<TheAnachron> Guest91: yep I did set that myself in my river running script.
<TheAnachron> Guest91 you probably should either run dbus as a user session or start it with river. Really depends on your setup. I have it set up as user service.
<Guest91> This is how I start it:
<Guest91> log_date=$(date +"%Y-%m-%d_%H-%M-%S")
<Guest91> log_file=$(mktemp -t river_"${log_date}".XXXXXXXXXX.log)
<Guest91> dbus-run-session -- sh -c "river -log-level debug > \"${log_file}\" 2>&1"
<Guest91> TheAnachron: Do you suggest something else?
Guest72 has quit [Quit: Client closed]
Guest22 has joined #river
<Guest91> ifreund: From xdg-desktop-portal-wlr troubleshooting checklist, everything checks out except that for (2), (3) and (4) I cannot run pipewire and xdg as services but rather processes. But they are running when I use `ps` to check.
<Guest91> Is there anyone that you know of using FreeBSD that I can get in touch with? I really don't know what I am missing. This is exactly the same process/setup I had using Hyprland where the screen sharing worked. The only thing that changed was changing xdg-desktop-portal-* from "hyprland" to "wlr".
<Guest22> Is there even stylus support in river?
<ifreund> it doesn't matter how pipewire and the xdg portal processes are started as long as they have the necessary environment variables
<ifreund> Yes, river has drawing tablet support but doesn't support pointer emulation
<ifreund> it only works with clients that have proper drawing tablet support
<ifreund> I do have a FreeBSD river install but haven't tried screen sharing with it yet
<ifreund> going to sleep now though, best of luck debugging :)
<Guest22> Ok how hard would that be to implement, is it worth to try implementing myself?
<Guest22> Thanks and Good night
<Guest91> ifreund: Do you know if these are enough? I can check your message tomorrow if you can respond.
<Guest91> export MOZ_ENABLE_WAYLAND=1
<Guest91> export XDG_CURRENT_DESKTOP=river
<Guest91> export XDG_RUNTIME_DIR=/var/run/user/`id -u`
<Guest91> export XDG_SESSION_TYPE=wayland
<Guest91> Also WAYLAND_DISPLAY is automatically set to wayland-1
<Guest91> If anyone can answer my last question I would be truly grateful. I will log on a bit later to check.
Guest91 has quit [Quit: Client closed]
Guest22 has quit [Ping timeout: 256 seconds]
Guest22 has joined #river
Guest22 has quit [Client Quit]