dnkl changed the topic of #foot to: Foot - fast, lightweight and minimalistic Wayland terminal emulator || 1.15.0 || https://codeberg.org/dnkl/foot || channel logs: https://libera.irclog.whitequark.org/foot
fraolt_ has quit [Ping timeout: 272 seconds]
fraolt_ has joined #foot
xd1le has quit [Quit: xd1le]
<dnkl> sewn: foot should exit, but not segfault
<sewn> well it occurs when I want to halt my system, and a signal is sent to all processes to suicide which also kills wayland and its sockets
<dnkl> if you can get a backtrace from a debug build, I'll take a look
<sewn> ok I'll see
avane_ has joined #foot
avane has quit [Ping timeout: 245 seconds]
avane_ is now known as avane
<dnkl> sewn: which signal is being sent to all processes? SIGTERM? Might be the signal that triggers the segfault, rather than the compositor dying.
<dnkl> fwiw, I can't reproduce. Neither by killing the compositor, nor by sending various signals to the foot process
xd1le has joined #foot
ayushnix has joined #foot
ayushnix has joined #foot
ayushnix has quit [Changing host]
ayushnix has quit [Remote host closed the connection]
ayushnix has joined #foot
ayushnix has joined #foot
ayushnix has quit [Changing host]
ayushnix has quit [Ping timeout: 246 seconds]
ayushnix has joined #foot
ayushnix has joined #foot
ayushnix has quit [Changing host]
ayushnix has quit [Remote host closed the connection]
<llyyr> I can reproduce it by sending SIGTERM to the foot process, but it only happens if the cursor is hovering on the foot window when you send the SIGTERM
<llyyr> I'll get a backtrace
<dnkl> llyyr: it doesn't reproduce on River. Which compositor are you running?
<llyyr> sway with the scene graph PR
<llyyr> I can try with master branch as well
<llyyr> Oh, can't reproduce on master
<llyyr> I guess it's a bug with the PR?
<dnkl> maybe, but not necessarily. Only way to tell is to try to figure out why it crashes...
<dnkl> the chain of events is: term_destroy() -> wayl_win_destroy() -> keyboard_leave() -> term_xcursor_update_for_seat() -> term_mouse_grabbed().
<dnkl> there we crash, because term_destroy() had already freed the key bindings associated with the terminal instance
<dnkl> we should be able to move the destruction of the key bindings until after the window has been destroyed
<llyyr> trace without optimized out just in case it's helpful https://0x0.st/HjkH.txt
vyryls has joined #foot
<dnkl> llyyr: thanks, that shows my guess was right: 'bindings' is null in the top most frame
<dnkl> I'd consider this a bug in foot. One could question wether it makes sense for the compositor to send a keyboard_leave event after the client explicitly unmapped the window. But doesn't really matter... this should be easy to handle in foot
<llyyr> thanks
ayushnix has joined #foot
ayushnix has joined #foot
ayushnix has quit [Changing host]
vyryls has quit [Quit: WeeChat 4.0.1]
<dnkl> llyyr: any chance you can test https://codeberg.org/dnkl/foot/pulls/1412?
ayushnix has quit [Ping timeout: 246 seconds]
ayushnix has joined #foot
ayushnix has joined #foot
ayushnix has quit [Changing host]
<llyyr> yep I'll give it a try in a sec
<llyyr> it fixes the crash, thanks for the quick fix
ayushnix has quit [Remote host closed the connection]
<Arnavion> (Also doesn't repro in sway 1.8.1)
shaniatwain has joined #foot
shaniatwain has quit [Quit: leaving]
xd1le has quit [Quit: xd1le]