01:14 <leon-p> andrew`: likely because wlroots is falling back to software rendering.

01:14 <leon-p> note that if you are interested in trying river out, a VM is overkill and just makes things needlessly complicated

01:14 <leon-p> river can run side-by-side or even inside your current desktop session

01:21 <andrew`> I unfortunately am constrainted to windows for a host OS which is the reason for the VM.

01:23 <andrew`> I am currently using dwl which works fine with the software rendering.

01:32 <leon-p> pretty sure both river and dwl use the wlroots scene graph for rendering, so there should not be any performance difference between them as far as rendering is concerned

01:33 <leon-p> what windows do you have open? firefox by any chance? The current transaction system can cause cursor movement stuttering if slow responding clients are present. Firefox often is in such a state for me at least

01:35 <andrew`> Just a terminal and emacs.

01:37 <andrew`> Even with no windows there is considerable lag in cursor movement.

02:17 <leon-p> weird

02:17 <leon-p> I know there is some mesa package for VMs that you are likely missing, just can't remember what it's called

05:31 <larstiq> https://docs.mesa3d.org/drivers/virgl.html ?

14:12 <gbrlsnchs> I'm observing an interesting behavior on 0.3.2 (so I'm updating to 0.3.5 to see if it's still the same). When river starts, the cursor is located in a HEADLESS output (I have 2 headless outputs set up), but keyboard focus is in the main output still. So if I spawn my fuzzy picker, it will open in the main output. But if I click the mouse before that, I lose focus to the headless output.

15:06 <bist> leon-p thanks. Will look into that

15:13 <bist> @leon-p in archcraft the config is init in the river folder. Then it calls swayidle which calls a script. Thanks for pointing me in the right direction

16:00 <tiosgz> gbrlsnchs: i think the cursor is initially somewhere near 0,0 in global coords, while keyboard focus is the first/last output

16:00 <tiosgz> (i even have riverctl focus-output next in my init from the times when i had two outputs)

16:01 <tiosgz> so you may be able to make it behave better by moving the outputs around

16:01 <gbrlsnchs> tiosgz: hmmm it might be the cursor is located at the leftmost output then... because one of my headless outputs is at -9999,-9999 lol

16:01 <gbrlsnchs> while the main one is at 0,0

16:02 <tiosgz> that may well be the case /shrug

16:02 <gbrlsnchs> but actually the cursor is starting at the headless output at +9999,+9999

16:03 <gbrlsnchs> anyway, I think I can script something to get around this behavior, it's not so annoying since I always start my session by opening the fuzzy picker anyway

16:04 <gbrlsnchs> but hey thanks for the hint tiosgz

16:05 <tiosgz> well one hack comes to mind lol: set-cursor-warp on-output-change, focus-output [headless-1], focus-output [headfull], set-cursor-warp [whatever-you-use] (yes that's ugly but may work)

16:26 <leon-p> ifreund: I see you decided to drop layer shell?

17:15 <geemili> andrew`: Another option for VM is Microsoft WSLg. It runs a weston compositor, and I think you can run river nested beneath it

18:03 <andrew`> geemili: Thanks, that looks promising. I think vmware makes it overly complicated. I tried comparing the wlroots logs of dwl and river and did not see anything obvious. glxgears is showing an order of magnitude difference between river and dwl so something must be going wrong on my end.

19:06 <TheAnachron> What, this is weird. I use kanshi for my displays, but when I set the scale to something higher than 1 it makes my terminals larger but my browser (firefox) shrinks very small. What

19:12 <rudyon> hello everyone

19:12 <rudyon> i have only recently started using river

19:13 <rudyon> i am also new to irc so please excuse my misuse of things

19:14 <rudyon> can anyone tell me how i am supposed to start xdg-desktop-portal-wlr i have been trying to set it up but can't get it to work. i am currently starting it from my river init file by running /usr/libexec/xdg-desktop-portal and /usr/libexec/xdg-desktop-portal-wlr with ampersand after them

19:15 <vyivel> pretty sure it's activated automatically

19:15 <andrew`> rudyon: Are you using dbus?

19:16 <rudyon> i am running river with dbus-run-session river which as far as i know is supposed to set up dbus?

19:18 <andrew`> rudyon: Those should be started automatically then as vyivel mentioned. You should not be starting them from the init file to my knowledge.

19:18 <rudyon> oh so me starting them from the init file is messing with them possibly?

19:18 <The_Buhs7> https://codeberg.org/bwbuhse/dotfiles/src/commit/59d381c7441daaf56161374b72eaa48a906597cd/river/.config/river/init-guile#L81 I just start them in my init, but also I’m not using systemd

19:19 <rudyon> i am also not using systemd

19:19 <rudyon> that's why i assumed i was supposed to start them aswell

19:20 <The_Buhs7> I can’t rn but I can try help you out more in like an hour if you don’t figure it

19:20 <andrew`> I thought dbus-daemon and not systemd was the automatic part.

19:21 <rudyon> The_Buhs7: thanks. i appreciate it. i'll try to figure it in the mean while

19:21 <The_Buhs7> I think I based my stuff off the sway page on the gentoo wiki

19:25 <rudyon> removing it from the init didn't fix it :( it would have been nice if it was so simple

19:26 <rudyon> this is unrelated to river but where can i learn general irc ettiquite?

19:28 <andrew`> rudyon: You may try starting with: "dbus-run-session -- river -log-level debug > /tmp/river.log 2>&1" to see if you get any messages from dbus-daemon about it in the log.

19:28 <rudyon> andrew`: i'll try doing that thank you

19:29 <andrew`> rudyon: You may try adding "dbus-update-activation-environment --all" to your init as well.

19:30 <rudyon> andrew`: i will try that too is it okay if i try both at the same time or should i try them one by one?

19:31 <andrew`> rudyon: I think trying them both is fine.

19:32 <rudyon> (^-^)b

19:33 <rudyon> oh it works now. kind of

19:34 <rudyon> yea it works

19:34 <rudyon> thank you so much andrew`

19:35 <rudyon> oh i failed to mention

20:06 <TheAnachron> is firefox broken on kanshi/river because of fractional scaling?

20:07 <TheAnachron> Ah, it seems to be a setting: widget.wayland.fractional-scale.enabled

20:17 <TheAnachron> even with that setting firefox misbehaves on fractional scaling. such a poor state we're in

20:23 <TheAnachron> Or is this an issue of river?

21:41 <ifreund> leon-p: yeah, it was getting in the way too much. It'll probably come back though as the commit message says

21:42 <ifreund> my goal right now is to get to a working river-window-management-v1 server asap so we can start actually playing with the protocol

21:46 <leon-p> fair

23:49 <Guest39> Hi there.