12:23 <carloratm> Hi all, is it possible to have sloppy focus on river?

12:36 <ifreund> carloratm: what is sloppy focus?

12:38 <carloratm> ifreund: focus that follows the mouse

12:39 <ifreund> carloratm: search for focus-follows-cursor in the riverctl man page

12:40 <carloratm> thx

12:42 <ifreund> no problem!

13:13 <NikhilSingh[m]1> `sudo systemctl restart ly`... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/65ec6aaec090e6ac1c822ed0c65cef68b73008bd)

13:13 <NikhilSingh[m]1> How can I restart a service without sudo.

15:13 <carloratm> How can I start waybar when river starts?

15:14 <plumeus> One option is to start it from `.config/river/init`

15:14 <plumeus> like, if you use a shell script, you could just put waybar inside the config

15:15 <carloratm> must be executed in background?

15:15 <plumeus> You could execute it any time

15:15 <plumeus> start river, open a terminal, run `waybar`

15:15 <plumeus> I just thought you meant that you wanted it to run automatically

15:16 <carloratm> I mean, in the init file, should I put waybar & ?

15:16 <plumeus> ah, yeah

15:16 <carloratm> ok

16:39 <NikhilSingh[m]1> How can I map a keybind to perform action with sudo.

16:41 <mizzunet> try pkexec

16:41 <hellmouth> Hello there. Really liking what I'm seeing with River, though I'm having some trouble with a monitor. I have two monitors connected to my laptop via a USB-C dock. In swaywm, both external monitors work. In River, however, only one works. The non-working one isn't visible in tools like wlr-randr, wlay, wlopm from inside River. My understanding

16:41 <hellmouth> is that both swaywm and river are using wlroots and that I can expect both monitors to be handled roughly the same (or is that not true?) Does anyone have any suggestions for how to debug a problem like this? I suppose that's more of a Wayland question, but I'm open to all suggestions. I doubt it's River-specific, but who knows?

16:42 <hellmouth> As soon as I saw the monitor wasn't even noticed by wlr-randr and wlopm, I sort of hit a dead end. It's strange that it works fine in swaywm.

16:44 <ifreund> hellmouth: what sway/river versions did you test? Do they use the same wlroots version?

16:44 <plumeus> "only one works", could you explain this?

16:44 <plumeus> I've used River with two monitors, worked fine for the most part.

16:44 <hellmouth> @ifreund good point, I'll check, one sec

16:45 <hellmouth> @plumeus My best description is that the monitor in question enters a disabled/sleeping power mode

16:46 <NikhilSingh[m]1> Ignore figured out.

16:47 <plumeus> I had weird interactions like how River wouldn't start if I booted my laptop with a display port inserted, or how River would freeze every few times I plugged my laptop to my monitor without restarting. Both were a bit weird and I never looked into the cause because I didn't use the monitor much.

16:47 <tleydxdy[m]> also maybe check the logs

16:50 <Guest59453453249> is there anyway I can have multiple keyboard layouts on river?

16:50 <Guest59453453249> right now the way you choose keyboard layout is specifying it as an environment variable

16:52 <Guest59453453249> so i tried using export XKBetc etc = "layout", hoping it would allow me to switch layouts on fly

16:52 <Guest59453453249> but yeah it didn't work unfortunately

16:52 <hellmouth> tleydxdy[m] I'd like to check the logs, though I haven't found any wayland logs or river logs

16:52 <leon-p> Guest59453453249: separate them with a comma and setup an xkb shortcut to switch between them

16:53 <leon-p> check the xkb manpages for more, can't remember how to do it exactly right now

16:53 <Guest59453453249> leon-p ah ok thanks

16:53 <tleydxdy[m]> hellmouth: they are just printed to stdout and stderr

16:56 <hellmouth> tleydxdy[m] Ah, ok, makes sense

16:59 <hellmouth> ifreund I believe the wlroots version is the same (0.15.1). It came from installing sway via arch's main repo, though I cloned River's github and compiled.

17:00 <hellmouth> In any case, it sounds like I should expect them to behave the same if these things are all the same. That makes me think I have some disparity somewhere

17:02 <hellmouth> Sorry, I'm new to Wayland and not too familiar with how it all comes together. I'll do some more troubleshooting. And tleydxdy[m] 's point about stderr and stdout is helpful -- I'll disable Ly and just start River from the TTY and see what I get

17:04 <ifreund> the best way to get logs would be running river from a tty and directing stderr/stdout to a file. For example `river > out.log 2>&1`

17:09 <hellmouth> yup

17:10 <hellmouth> Thanks everyone, I think at least knowing I can stop hunting for log files and also that it's expected that the monitors *should* be handled the same, all things considered equal, is enough to get me started

18:09 <hellmouth> Hm. Looks like the monitor in question isn't sending a modeset when wlroots requests it

19:17 <hellmouth> Okay, it ended up being a bandwidth issue with my USB-C dock, as the monitor works when it's the only one connected to the dock. This is also an issue for me in X11, but X11 will at least recognize it so I can reduce the refresh rate of the monitor with xrandr. I'm not sure what sway is doing differently. Looks like there's at least one other

19:17 <hellmouth> person with this problem: https://github.com/riverwm/river/issues/502

19:23 <tiosgz> hellmouth: would be nice if you could leave a comment on that issue with your discoveries

19:25 <hellmouth> Yup, just did

19:25 <tiosgz> thanks

19:31 <ifreund> hellmouth: it might help to compare debug logs with sway here under the conditions where sway works but river doesn't, feel free to attach logs to the issue and I'll take a look when I have time

19:32 <hellmouth> Yeah, I just added some additional information to my comment. Unfortunately, sway wasn't as verbose when I tried running it last. I'll double-check that I didn't mess up the redirection

19:33 <ifreund> passing -d to sway should make it more verbose

19:33 <hellmouth> Ah, cool, I'll try it

19:33 <ifreund> and -log-level debug to river wouldn't hurt either

19:34 <hellmouth> For what it's worth, this issue is squarely with me and my setup. This ultrawide monitor has been problematic in X11 with its modelines and this USB-C dock doesn't help matters

19:36 <hellmouth> It's this weird Acer monitor that was sold under two model names (XV340CK and XV340CK P) and I've had EDID issues with it

19:46 <ifreund> could be a hardware/driver issue indeed, what makes me curious though is that both you and the other person who opened that issue reported it working on sway