10:24 <baltazar> hi! I sometimes have foot randomly freeze. in this state, pressing a key unfreezes it, but moving the mouse doesn't do anything. if the mouse was hidden (due to [mouse] hide-when-typing=yes), foot doesn't unhide it when moving (checking WAYLAND_DEBUG=1 logs, I can see that foot still does receive mouse motion events)

10:51 <dnkl> do a debug build and attach with gdb when it "freezes" and see where it is stuck?

10:52 <baltazar> dnkl: the problem is, it unfreezes on its own after a bit as well

10:53 <dnkl> baltazar: sounds like it's not stuck at all. sounds more like a graphics driver issue. or possibly compositor issue. which compositor?

10:53 <baltazar> sway

10:54 <baltazar> but I'm pretty sure something's stuck inside foot as well... normally when I start moving the mouse, foot unhides it, but when it freezes, it doesn't

10:55 <baltazar> and it's not just that I don't see the mouse, checking debug logs, I can see that it only sends the things needed to show the mouse once it visibly unfreezes

10:56 <dnkl> then you need to attach gdb and check where it's stuck

10:56 <dnkl> no way around it

10:57 <baltazar> all right, I'll try

10:58 <dnkl> baltazar: you're on foot 1.13.1?

10:58 <baltazar> master

10:59 <dnkl> Linux or bsd?

10:59 <baltazar> linux

10:59 <dnkl> and fcft is also up to date?

11:00 <dnkl> remember you may be linking it statically if you build foot yourself

11:00 <dnkl> (from subprojects/fcft)

11:00 <baltazar> I'm linking dynamically, though not to fcft master. I'm on fcft 3.1.4

11:01 <dnkl> alright. then there are no known performance issues

11:01 <dnkl> half-freezing like that suggests a flood of something. compositor events, for example.

11:02 <baltazar> I don't see anything weird in the debug logs. if I don't move the mouse, then literally nothing happens while it's frozen

11:03 <dnkl> are you on sway master, or an actual release?

11:04 <baltazar> master, plus some patches applied. but I had this issue on "vanilla" master as well

11:04 <dnkl> you could try downgrading to 1.7 and see if that "fixes" it

11:20 <dnkl> baltazar: hmm, it kind of sounds like foot isn't receiving any frame callbacks

11:20 <dnkl> that would explain both the apparent freeze, and the pointer remaining hidden

11:20 <dnkl> i think 😅

12:40 <novakane> for some reasons recently, using zoxyde to change dir, using Ctl-shift-n no longer open the new instance in the CWD

12:40 <novakane> works fine if I just use `cd path/to/dir`

12:42 <novakane> zoxide*

12:46 <baltazar> dnkl: is there an easy way to verify that?

12:56 <dnkl> baltazar: might be possible to see if the are no frame callbacks (using WAYLAND_DEBUG) when moving the cursor. Depends a bit on how it looks like when everything is working

12:56 <dnkl> looking for missing callbacks for normal window updates is probably futile (too many of them)

13:42 <baltazar> dnkl: it looks exactly the same. foot receives wl_pointer@22.frame() and wl_pointer@22.motion(...) events as I move the mouse

13:51 <dnkl> baltazar: is foot burning CPU while stuck? If not, best guess it's waiting for something that never arrives

13:53 <baltazar> hmm, I just noticed, when it unfreezes, I see this (twice) in the debug log: discarded [unknown]@33.[event 0](0 fd, 12 byte)

13:59 <dnkl> possibly a libwayland issue then. Looks like the event stream either gets corrupt, or compositor is sending something libwayland doesn't understand

19:45 <kabouik> Where can I find a list of correct license abbreviations for packages? Apparently one of the patchset I have sent have is off on that regard

19:45 <kabouik> Woops, wrong channel. Apologies.