Wayfire crashed when resume from suspend without extra monitor

[shootheart]

Describe the bug
wayfire will crash when the system resumes from suspend with extra monitor disconnected.

To Reproduce
Steps to reproduce the behavior:

1. keeping an extra monitor (such as HDMI) connect, execute systemctl suspend.
2. disconnect the monitor during system suspended.
3. wakeup system (which I did was open the laptop lid).
4. wayfire crashed and returned to display manager.

Expected behavior
It should resume normal.

Screenshots or stacktrace
I've get the debug logs as follow:

II 24-09-24 23:03:14.715 - [backend/drm/drm.c:1552] Scanning DRM connectors on /dev/dri/card1
II 24-09-24 23:03:14.719 - [backend/drm/drm.c:1636] 'HDMI-A-1' disconnected
II 24-09-24 23:03:14.720 - [wayfire-0.9.0/src/core/output-layout.cpp:1212] remove output: HDMI-A-1
EE 24-09-24 23:03:14.720 - [wayfire-0.9.0/src/core/output-layout.cpp:533] disabling output: HDMI-A-1
II 24-09-24 23:03:14.720 - [wayfire-0.9.0/src/core/output-layout.cpp:163] transfer views from HDMI-A-1 -> eDP-1
II 24-09-24 23:03:14.722 - [backend/drm/drm.c:790] connector HDMI-A-1: Turning off
II 24-09-24 23:03:14.757 - [backend/drm/drm.c:786] connector eDP-1: Modesetting with 1920x1080 @ 60.049 Hz
EE 24-09-24 23:03:14.790 - [wayfire-0.9.0/src/main.cpp:141] Fatal error: Segmentation fault
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
> Warning:          Could not resolve keysym XF86KbdInputAssistPrevgrou
> Warning:          Could not resolve keysym XF86KbdInputAssistNextgrou
Errors from xkbcomp are not fatal to the X server
EE 24-09-24 23:03:14.821 - #1  wf::print_trace(bool) ??:?
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
> Warning:          Could not resolve keysym XF86KbdInputAssistPrevgrou
> Warning:          Could not resolve keysym XF86KbdInputAssistNextgrou
Errors from xkbcomp are not fatal to the X server
EE 24-09-24 23:03:14.843 - #2  __sigaction ??:?
EE 24-09-24 23:03:14.863 - #3  wlr_addon_find ??:?
EE 24-09-24 23:03:14.882 - #4  wlr_output_layout_get ??:?
EE 24-09-24 23:03:14.900 - #5  wlr_output_layout_get_box ??:?
EE 24-09-24 23:03:14.927 - #6  wf::output_t::get_layout_geometry() const ??:?
EE 24-09-24 23:03:14.954 - #7  wf::scene::output_node_t::get_bounding_box() ??:?
EE 24-09-24 23:03:14.979 - #8  wf::wlr_surface_controller_t::update_subsurface_order_and_position() ??:?
EE 24-09-24 23:03:15.004 - #9  std::_Function_handler<void (wf::signal::connection_base_t*&), wf::signal::provider_t::emit<wf::view_fullscreen_request_signal>(wf::view_fullscreen_request_signal*)::{lambda(wf::signal::connection_base_t*)#1}>::_M_manager(std::_Any_data&, std::_Any_data const&, std::_Manager_operation) ??:?
EE 24-09-24 23:03:15.022 - #10 wl_signal_emit_mutable ??:?
EE 24-09-24 23:03:15.040 - #11 wlr_surface_get_effective_damage ??:?
EE 24-09-24 23:03:15.058 - #12 ffi_prep_go_closure ??:?
EE 24-09-24 23:03:15.075 - #13 ?? ??:0
EE 24-09-24 23:03:15.095 - #14 ffi_call ??:?
EE 24-09-24 23:03:15.113 - #15 ?? ??:0
EE 24-09-24 23:03:15.132 - #16 wl_client_destroy ??:?
EE 24-09-24 23:03:15.150 - #17 wl_event_loop_dispatch ??:?
EE 24-09-24 23:03:15.167 - #18 wl_display_run ??:?
EE 24-09-24 23:03:15.192 - #19 main ??:?
EE 24-09-24 23:03:15.213 - #20 __libc_init_first ??:?
EE 24-09-24 23:03:15.234 - #21 __libc_start_main ??:?
EE 24-09-24 23:03:15.259 - #22 _start ??:?
(EE) failed to read Wayland events: Connection reset by peer

Wayfire version
0.9.0-c4236d6 (Sep 17 2024) branch master (from AUR repo)