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/
elshize has quit [Quit: elshize]
hspak9 has joined #river
hspak has quit [Ping timeout: 256 seconds]
hspak9 is now known as hspak
hspak has quit [Quit: Ping timeout (120 seconds)]
hspak has joined #river
andyrtr_ has joined #river
andyrtr has quit [Ping timeout: 252 seconds]
andyrtr_ is now known as andyrtr
andyrtr has quit [Ping timeout: 264 seconds]
andyrtr has joined #river
eShaev9z_ has joined #river
eShaev9z has quit [Ping timeout: 255 seconds]
waleee has quit [Ping timeout: 260 seconds]
peelz has quit [Ping timeout: 245 seconds]
peelz has joined #river
peelz has quit [Changing host]
peelz has joined #river
peelz has quit [Client Quit]
peelz has joined #river
peelz has quit [Changing host]
peelz has joined #river
peelz has quit [Ping timeout: 276 seconds]
<ifreund> NickH: that stack trace isn't terribly useful without debug symbols sadly
<ifreund> in any case, swaylock crashing is almost certainly a swaylock bug
<ifreund> if you suspect a change in behavior on river's side, comparing a WAYLAND_DEBUG=1 log from before to one where swaylock crashes would be the best way to debug that
<ifreund> It could possibly be related to https://github.com/riverwm/river/issues/915 but I don't know of any other issues on river's side that might be relevant
orfeas has joined #river
<NickH> ifreund: thanks for the hints. I just install the debug symbols for swaylock. If it crashes again I should have more information, if it doesn't, that's good too.
<NickH> s/install/installed
<dnkl> ifreund: really nice to see both fractional scaling and server-side cursors, thanks!
TheAnachron has joined #river
orfeas has left #river [WeeChat 4.0.4]
orfeas has joined #river
<LarstiQ> ifreund: is it too late to point out typos in the commit messages? (e.g. s/ther/the/)
traidare has joined #river
<TheAnachron> one can always do a git amend, so no.
<LarstiQ> but rewriting published master is not so nice for other people's checkouts, so depends on the project policy
cyph3r has joined #river
leopoldek has quit [Remote host closed the connection]
cyph3r has quit [Ping timeout: 256 seconds]
cyph3r has joined #river
traidare has quit [Ping timeout: 260 seconds]
cyph3r has quit [Ping timeout: 276 seconds]
cyph3r has joined #river
cyph3r has quit [Ping timeout: 264 seconds]
cyph3r has joined #river
cyph3r has quit [Ping timeout: 260 seconds]
cyph3r has joined #river
cyph3r has quit [Ping timeout: 246 seconds]
cyph3r has joined #river
cyph3r has quit [Ping timeout: 260 seconds]
cyph3r has joined #river
traidare has joined #river
cyph3r has quit [Ping timeout: 252 seconds]
cyph3r has joined #river
Misthios has quit [Quit: Misthios]
cyph3r has quit [Ping timeout: 276 seconds]
cyph3r has joined #river
traidare has quit [Ping timeout: 276 seconds]
cyph3r has quit [Ping timeout: 255 seconds]
cyph3r has joined #river
cyph3r has quit [Remote host closed the connection]
traidare has joined #river
mx08 has quit [Remote host closed the connection]
mx08 has joined #river
orfeas has quit [Quit: WeeChat 4.0.4]
dvzrv has quit [Ping timeout: 256 seconds]
dvzrv has joined #river
moomoomoo has joined #river
<moomoomoo> I'm trying to set tap-to-click for my touchpad, is this config correct? riverctl input "Synaptics s3203" tap enabled
<moomoomoo> I mean what's would be the correct way to do it, the above is not working.
moomoomoo has quit [Quit: Client closed]
moomoomoo has joined #river
<moomoomoo> How do I setup tap-to-click for my touchpad?
<moomoomoo> It's mentioned on riverctl man page, but can't make it work
<moomoomoo> my device name is "Synaptics s3203"
cyph3r has joined #river
cyph3r has quit [Remote host closed the connection]
moomoomoo has quit [Quit: Client closed]
<novakane> moomoomoo: that's the name given in `riverctl list-inputs`? Because that don't look like it
moomoomoo has joined #river
moomoomoo has quit [Client Quit]
tiosgz has joined #river
<tiosgz> 1) NickH: if it's the same swaylock binary, i think you could try and get the stack trace once more from the same coredump
<tiosgz> 2) maybe related to #953 (frac scale rounding error): with my usual scale of 1.25, opening a nested river with foot makes it blurry
<tiosgz> perhaps there should be a warning for packagers to potentially patch it away until clients have improved?
<tiosgz> or maybe it's just that the wlroots wayland backend doesn't speak frac scale / pass it to its clients? actually seems to be this case.
<tiosgz> 3) not really river's fault, but browsers don't like fr-sc either: qute is pixelated, firefox (with the widget.wayland.* config) messes up popups
<tiosgz> ooh, nice, now i know why i shouldn't prepare sequences of messages and copy-paste them.
<tiosgz> the order is: 1), 2), "^or maybe", 3), "^perhaps"
<tiosgz> sorry about that
tiosgz has quit [Quit: tiosgz]
Guest52 has joined #river
TheAnachron has quit [Quit: TheAnachron]
traidare has quit [Ping timeout: 260 seconds]
Guest52 has quit [Quit: Client closed]
traidare has joined #river
Szadek has quit [Quit: off]
Szadek has joined #river
ccha has quit [Quit: WeeChat 4.1.2]
ccha has joined #river
waleee has joined #river
Cornelius-Figgle has quit [Remote host closed the connection]
orfeas has joined #river
Cornelius-Figgle has joined #river
<ifreund> tiosgz: As you may have seen already, I've opened some upstream wlroots issues to discuss the fractional scaling issues
<ifreund> I don't think it's very likely that clients supporting the protocol are messing up to be honest
<ifreund> if it's really a downgrade to have the fractional scaling protocol enabled we could put it behind some kind of debug option for now until the situation upstream for wlr_scene improves
leopoldek has joined #river
orfeas has quit [Ping timeout: 245 seconds]
Szadek has quit [Quit: off]
Szadek has joined #river
traidare has quit [Ping timeout: 240 seconds]
<alebastr> ifreund: how about trying case-sensitive first and falling back to insensitive? surely, that won't make things worse
<alebastr> actually, it might... there's about ~300 keysyms ambiguous with case-insensitive match, including a-z. how does that even work?
<ifreund> alebastr: yeah, and the example init file uses uppercase for A-Z, relying on the match returning the lowercase variant for things to work properly
<ifreund> trying case-sensitive first would break `riverctl map normal Super A exit` for example
<ifreund> It's a massive mess
<ifreund> I love how this issue has just found the counterexample to this comment: https://github.com/xkbcommon/libxkbcommon/blob/31ebe0037bf25ba24a93c4d0f033943742a3ee74/src/keysym.c#L151-L155
<ifreund> if the comment were correct, thing would actually be fine I think
<ifreund> alebastr: did you generate a list of ambiguous symbols perchance? I wouldn't mind a look if so
<alebastr> ifreund: https://0x0.st/H6Et.txt
<ifreund> thanks!
<ifreund> damn, I think Screensaver/ScreenSaver really is the only pair that's not a capitalization thing
<ifreund> perhaps the right fix is just special casing that
<ifreund> By "not a capitalization thing" i meant that it's the only pair where the uppercase variant is not a Shifted version of the lowercase variant
<ifreund> everything else in there is alphabetic symbols with upper/lower case variants
Guest76 has joined #river
Guest76 has quit [Client Quit]