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/
waleee has quit [Ping timeout: 260 seconds]
waleee has joined #river
kotto has quit [Quit: WeeChat 4.0.5]
eShaev9z has quit [Ping timeout: 248 seconds]
eShaev9z_ has joined #river
waleee has quit [Ping timeout: 272 seconds]
angry_vincent has joined #river
leopoldek has quit [Ping timeout: 248 seconds]
kotto has joined #river
uncomfy has quit [Ping timeout: 252 seconds]
uncomfy has joined #river
tmpm697 has joined #river
uncomfy has quit [Ping timeout: 252 seconds]
uncomfy has joined #river
captainchris has joined #river
<captainchris> Hi everybody
<captainchris> It is possible to configure border thickness ??
captainchris has quit [Quit: Lost terminal]
<ifreund> yes, see the riverctl man page
tmpm697 has quit [Quit: Client closed]
uncomfy has quit [Remote host closed the connection]
ayushnix has joined #river
leopoldek has joined #river
leopoldek has quit [Remote host closed the connection]
waleee has joined #river
waleee has quit [Ping timeout: 240 seconds]
tiosgz has joined #river
<tiosgz> ifreund: been wondering for a while if i should tell you to s/(flags)(.*)(tag)/\3\2\1/ in #796 (0.3 tracking issue)
<tiosgz> or actually (flag)(.*)(tag), as the 's' is correct there
Guest22 has joined #river
Guest22 has quit [Client Quit]
maralorn has joined #river
<maralorn> Hey there! I am trying to launch some daemons (eww, kanshi) via systemd user units, while using river.
<maralorn> At least for eww this worked with hyprland.
<maralorn> Now it fails to start with ERROR eww::error_handling_ctx > Failed to initialize GTK.
<maralorn> My assumption is that the application in in the systemd unit does not know how to find the wayland compositor to connect to.
<maralorn> Now I am wondering how do wayland clients discover the compositor.
<maralorn> I have this line in my config, but it does not seem to help: dbus-update-activation-environment --systemd DISPLAY WAYLAND_DISPLAY XDG_CURRENT_DESKTOP XDG_SESSION_TYPE
<tiosgz> iirc usually there's some messing-around with "graphical-session" or something as a dependency for these units, and then telling systemd that graphical-session is available
<tiosgz> can't find any concrete stuff now, though
<tiosgz> hyprland's thing, idk details on what to do with it https://github.com/hyprwm/Hyprland/blob/main/example/hyprland.service
maralorn15 has joined #river
maralorn has quit [Ping timeout: 245 seconds]
maralorn15 has quit [Ping timeout: 245 seconds]
maralorn has joined #river
<maralorn> I don’t see how all this graphical-session thing should influence the ability of a unit to start. Yes, of course I need to find a way to start all the units I want in the right order.
<maralorn> But a program should just be able to launch if I do systemctl --user start
<tiosgz> oh, i thought you were already trying to autostart it. sorry, my confusion
<tiosgz> i wonder if that dbus-... thing needs to be done for systemd as well
tiosgz has quit [Quit: tiosgz]
maralorn has quit [Quit: Client closed]
maralorn has joined #river
<maralorn> Ah, I started river with launch-dbus-session and that was a mistake because systemd used another dbus session.
<maralorn> So the WAYLAND_DISPLAY variable was not set correctly.
maralorn has quit [Quit: Client closed]
notzmv has quit [Ping timeout: 260 seconds]
angry_vincent has quit [Remote host closed the connection]