notzmv has quit [Remote host closed the connection]
snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
waleee has joined #river
notzmv has joined #river
waleee has quit [Ping timeout: 240 seconds]
waleee has joined #river
snakedye has quit [Ping timeout: 240 seconds]
snakedye has joined #river
waleee has quit [Ping timeout: 240 seconds]
arun has joined #river
mon_aaraj has joined #river
<daurn>
ifreund: FYI still not having any luck, even after updating to nvidia 510
<ifreund>
daurn: I was in a bit of a rush last time and forgot to ask for debug logs, could you try with `river -log-level debug`?
<daurn>
under X? nothing new
<ifreund>
running from a tty might be more informative
<daurn>
in a tty... also nothing new
<ifreund>
daurn: are you using wlroots 0.15.0 or 0.15.1? I think there may be a relevant fix in 0.15.1
<daurn>
ah, running 0.15.0
<daurn>
updated to 0.15.1 now
<daurn>
nothing different under X
<ifreund>
hmm, it could be that the nvidia driver doesn't support GBM on your specific hardware. I'm not really sure what the state of things is but I've mostly heard that it's still incomplete/buggy despite Nvidia making steps in the right direction
<daurn>
though other wayland stuff seems to work without doing that: does river require KMS where other compositors don't?
<ifreund>
daurn: other wayland stuff being what exactly?
<ifreund>
river doesn't do anything different from other wlroots based compositors here as far as I'm aware
<daurn>
it was a couple of months ago now but I was playing with other wayland desktops. I can't remember now :/
<daurn>
brb turning on KMS
waleee has joined #river
gwizon has quit [Ping timeout: 256 seconds]
gwizon has joined #river
<daurn>
okay that did work! sort of
<daurn>
river was able to start, and I saw my sway bar
<daurn>
however I didn't have a mouse
<ifreund>
hmm, could try WLR_NO_HARDWARE_CURSORS=1
<daurn>
I *thought* my keyboard shortcuts weren't working. but after switching to another VT and looking, it seems they *are*, but stuff isn't showing up
<daurn>
e.g. I have a keyboard shortcut to open urxvt... and I see them running in `ps` with bash children
<daurn>
but nothing showing up in river
<ifreund>
anything interesting in debug logs?
<leon-p>
urxvt is not Wayland native IIRC, so maybe an XWayland issue. Try using a terminal with Wayland support instead and see if that works
<daurn>
ifreund: only thing in debug logs is when I swap away from the VT with river, it shows lots of "removed input device"
<daurn>
leon-p: correct it would be via XWayland. I *do* see XWayland running
<daurn>
How do I use `riverctl` from my X session targeting my river session?
<ifreund>
daurn: set WAYLAND_DISPLAY=wayland-1
<ifreund>
or whatever number display river created in $XDG_RUNTIME_DIR
<leon-p>
daurn: XWayland running does not mean it does not have issues, I still recommend trying a Wayland native terminel, like foot.
<daurn>
leon-p: k; working on getting foot working...
<daurn>
so running `WAYLAND_DISPLAY=wayland-1 foot` from my X session did make foot pop up in river... still no mouse. and then foot crashed :/
<leon-p>
well, foot crashing means one more log that could shed light on what happens here, so it's progress
<dnkl>
No seat?
gwizon has quit [Ping timeout: 250 seconds]
<dnkl>
(that's been one crash reason for foot - should be fixed in master)
<ifreund>
setting WAYLAND_DEBUG=1 for river logs is a little too verbose usually
<ifreund>
wlroots is certainly using your nvidia card there though
<daurn>
lines 11181 to 11209 seem to have a little info about the Xwayland failure
<ifreund>
11207 seems to explain why you don't see a cursor
<ifreund>
well, urxvt works fine under xwayland on my AMD hardware...
arun has quit [Quit: arun]
<tiosgz`>
what type+value should i use for a zig-wayland listener last arg if i don't need to pass anything around? (void + {} complains it isn't a pointer)
elshize has quit [Ping timeout: 240 seconds]
elshize has joined #river
<ifreund>
tiosgz`: I use ?*anyopaque and pass null as the value
<ifreund>
it's not ideal, but It's simpler than the alternatives I tried
<ifreund>
we could use comptime to translate void + {} into ?*anyopaque + null I suppose, feel free to give that a go if you like
<tiosgz`>
aye, that works. thanks!
<ifreund>
We do something kind of similar for wl.Listener(void) currently iirc
<waleee>
have you already migrated to anyopaque? Wasn't that a somewhat recent (post 0.9) change
<waleee>
ah, no it was in 0.9
<ifreund>
yeah, I snuck it in a few days before 0.9.0 was tagged
elshize has quit [Ping timeout: 256 seconds]
elshize has joined #river
<ifreund>
so #519 is a real can of worms to solve properly
<ifreund>
yep, I'm just going to refactor this away during the wlr scene migration I think
<ifreund>
leon-p: congats on the first breaking change in river's history :D
<leon-p>
yay :D
<novakane>
worth a github achievements on your profile :P
<leon-p>
more will probably come eventually, but this and next semester are kinda important :/
<novakane>
ifreund: could you make the issue river 0.2.0 where only can write? So people could subscribe to it and get a notif when there is a new thing, not sure if that the case when you edited the first message
<novakane>
ah wait that already tha case, my bad
<ifreund>
I don't think github sends notifications on updates, not sure though
<ifreund>
s/updates/edits/
<novakane>
yeah I don't think so, that's why new comments are better
<leon-p>
isn't 745fe829 also breaking, technically? I don't think anyone depended on that behaviour, since it was a wrong impl. of the protocol, but it is a behaviour change
<ifreund>
i don't consider bugfixes like that breaking
<ifreund>
linus would I guess, but river's no where near the level of maturity where I would consider taking that stance
<ifreund>
anyhow, 0.1.3 is already tagged :D
<dnkl>
that input naming change got me for a while...
<ifreund>
I think it will be worth it for the edge cases it drastically improves
<ifreund>
dnkl: looks like today was release day for you too! time to update the void packages :)
<dnkl>
yup, finally found the hours I needed for this :)
groknull has joined #river
groknull has quit [Remote host closed the connection]