dnkl changed the topic of #foot to: Foot - fast, lightweight and minimalistic Wayland terminal emulator || 1.12.1 || https://codeberg.org/dnkl/foot || channel logs: https://libera.irclog.whitequark.org/foot
caveman has quit [Remote host closed the connection]
caveman has joined #foot
kevr has quit [Remote host closed the connection]
kevr has joined #foot
kevr has quit [Remote host closed the connection]
kevr has joined #foot
brocellous has quit [Read error: Connection reset by peer]
brocellous has joined #foot
radu242 has quit [Ping timeout: 276 seconds]
radu242 has joined #foot
caveman has quit [Ping timeout: 240 seconds]
caveman has joined #foot
pranjhol has joined #foot
pranjhol is now known as brunoBuccellati
<baltazar> dnkl: I don't think the slow start with external monitor is a sway issue, as it only seems to affect foot
<dnkl> baltazar: can you run foot with WAYLAND_DEBUG=1 and see where it stalls?
<baltazar> I've tried, but it's not really obvious. like, it doesn't stall for seconds, just takes visibly longer to start up
<baltazar> what's the unit of the timestamps supposed to be btw? milliseconds?
brunoBuccellati has quit [Quit: Client closed]
<baltazar> oh wait, I think I've found it
<baltazar> "wl_surface@3.enter(wl_output@18)": +0.003 vs +195.322
<baltazar> (had to create some ugly sed script to show diff timestamps instead of absolute otherwise I couldn't find the culprit :P)
<dnkl> is there a difference if you set dpi-aware=no?
<baltazar> dnkl: already have it
<baltazar> should I try with =yes?
<dnkl> nah
<dnkl> are there different scaling factors on the two monitors?
<baltazar> nope, but in this setup my laptop monitor isn't even enabled
<dnkl> so you're saying you have a single monitor enabled (not just power-saving, but disabled), and foot is starting slower?
<baltazar> yep
<dnkl> there's no way that is on foot
<dnkl> just to be *absolutely* sure... foot's log output is only listing a single monitor?
<dnkl> this has to be related to the GPU drivers, or something like that. Not sure what other applications you're comparing with, but I think it's important that those you compare with is *not* GPU accelerated. As otherwise you'll be hitting different code paths in the compositor
<baltazar> hmm, ok. I've tested with `imv` and `xkbcli interactive-wayland`, neither takes noticable time to appear. any other wayland stuff that start "immediately"?
<dnkl> one more thing you can try, I guess, is setting tweak.max-shm-pool-size-mb=0
<baltazar> doesn't seem to be any better
<baltazar> though now the the extra 200ms is at `wl_display@1.delete_id(30)`
<baltazar> oh, apparently this happens without that option too, so... (not like I know what it means)
<dnkl> most likely that the delay is somewhere else in the system. I still suspect the graphics stack. That means the exact point where it shows up in foot varies
<dnkl> as long as there's only a single monitor enabled, foot will do the *exact* same things, regardless of which monitor it is
cem has left #foot [#foot]
caveman has quit [Quit: bbl]
caveman has joined #foot