Segmentation fault on Raspberry Pi Trixie (Debian)

no errors during installation

 $ sudo apt install wcm
Installing:                     
  wcm

Installing dependencies:
  libwf-config1  wdisplays

Summary:
  Upgrading: 0, Installing: 3, Removing: 0, Not Upgrading: 4
  Download size: 528 kB
  Space needed: 2,900 kB / 228 GB available

Continue? [Y/n] y
Get:1 http://deb.debian.org/debian trixie/main arm64 libwf-config1 arm64 0.9.0-2 [122 kB]
Get:2 http://deb.debian.org/debian trixie/main arm64 wcm arm64 0.9.0+repack-2 [363 kB]
Get:3 http://deb.debian.org/debian trixie/main arm64 wdisplays arm64 1.1.1-1+b2 [43.1 kB]
Fetched 528 kB in 1s (851 kB/s)     
Selecting previously unselected package libwf-config1:arm64.
(Reading database ... 144875 files and directories currently installed.)
Preparing to unpack .../libwf-config1_0.9.0-2_arm64.deb ...
Unpacking libwf-config1:arm64 (0.9.0-2) ...
Selecting previously unselected package wcm.
Preparing to unpack .../wcm_0.9.0+repack-2_arm64.deb ...
Unpacking wcm (0.9.0+repack-2) ...
Selecting previously unselected package wdisplays.
Preparing to unpack .../wdisplays_1.1.1-1+b2_arm64.deb ...
Unpacking wdisplays (1.1.1-1+b2) ...
Setting up wdisplays (1.1.1-1+b2) ...
Setting up libwf-config1:arm64 (0.9.0-2) ...
Setting up wcm (0.9.0+repack-2) ...
Processing triggers for hicolor-icon-theme (0.18-2) ...
Processing triggers for gnome-menus (3.36.0-3) ...
Processing triggers for libc-bin (2.41-12+rpt1) ...
Processing triggers for mailcap (3.74) ...
Processing triggers for desktop-file-utils (0.28-1) ...

Segmentation Fault

$ wcm
II 20-01-26 17:33:16.302 - [src/file.cpp:579] Reading XML configuration options from directory /usr/share/wayfire/metadata
II 20-01-26 17:33:16.302 - [src/file.cpp:579] Reading XML configuration options from directory /usr/share/wayfire/metadata/wf-shell
Compositor does not advertise zwp_keyboard_shortcuts_inhibit_manager_v1
Binding grabs will not work
Segmentation fault

Reproduce the crash by running wcm on Raspberry Pi Trixie after installing the Debian packages shown, and compare the startup output with the reported log. Trace the startup path from the compositor capability warning to the segmentation fault; done means wcm starts without crashing on this environment.