<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
<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