Segmentation fault on Raspberry Pi Trixie (Debian)

[theoldwizard1]

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

[soreau]

It's not supposed to segfault, but does it help if you enable Keyboard Shortcuts Inhibit plugin, a.k.a. shortcuts-inhibit via the wayfire config file ~/.config/wayfire.ini?

[theoldwizard1]

it would be NICE if you documented/linked how to "enable Keyboard Shortcuts Inhibit plugin" in ~/.config/wayfire.ini

[soreau]

it would be NICE if you documented/linked how to "enable Keyboard Shortcuts Inhibit plugin" in ~/.config/wayfire.ini

Sure. You add shortcuts-inhibit to the list of plugins in the [core] section of ~/.config/wayfire.ini. For example:

[core]
...
plugins = shortcuts-inhibit ...
...

Note that the ellipses are placeholders for other potentially existing config syntax.

[theoldwizard1]

Thanks ! Still learning wayfire. any good docs ?

[NamorNiradnug]

Thanks ! Still learning wayfire. any good docs ?

WCM shows and allows to set almost all the available options.
There are some docs on the wiki, but AFAIK they are a little outdated.

[soreau]

Thanks ! Still learning wayfire. any good docs ?

WCM shows and allows to set almost all the available options. There are some docs on the wiki, but AFAIK they are a little outdated.

... only if WCM is crashing so it cannot be used, this is a nonstarter. 😅

[NamorNiradnug]

By the way, I don't experience WCM crashing when the protocol is disabled (with upstream wayfire and WCM on x86-64).
@theoldwizard1 Could you please try upstream WCM and see whether it crashes?

[soreau]

By the way, I don't experience WCM crashing when the protocol is disabled (with upstream wayfire and WCM on x86-64). @theoldwizard1 Could you please try upstream WCM and see whether it crashes?

I was thinking this as well but latest wcm git master will not build against wayfire 0.9 unless you remove or modify the wayfire version requirement.

[theoldwizard1]

By the way, I don't experience WCM crashing when the protocol is disabled (with upstream wayfire and WCM on x86-64).

Irrelevant ! We are talking RPi OS (Debian) on ARM !

[soreau]

@theoldwizard1 The best way to know what is going on when an application is segfaulting is to look at the backtrace of the crash. Also, it is possible that this crash has already been fixed upstream. So, here are some things to try:

1. Attempt to acquire a backtrace from the currently installed wcm 0.9.x. To do this, we will use gdb. Make sure gdb is installed and then perform these steps:

• Run gdb wcm
• When the program crashes, you should be at a gdb prompt. Type bt full and press enter.
• You should see a backtrace. Press enter until you are back at the gdb prompt.
• Copy the entire backtrace and post it here.

2. Try latest wcm to see if the crash has already been fixed upstream. To do this, perform these steps:

• Install development packages with sudo apt install wayfire-dev meson ninja-build
• Clone latest wcm, patch, build and install it using cd /tmp && git clone https://github.com/wayfirewm/wcm wcm-git && cd wcm-git && curl https://0x0.st/PPyl.diff | git apply && meson setup --prefix=/tmp/wcm build && ninja -C build install
• Run the newly installed wcm and see if it works or crashes with /tmp/wcm/bin/wcm

3. If the newly installed wcm crashes as well, run it under gdb and get the backtrace and then post the backtrace here.

• gdb /tmp/wcm/bin/wcm
• bt full
• Press enter until reaching the gdb prompt.
• Copy the entire backtrace and post it here.

Hopefully, this will help us get to the bottom of why wcm is crashing.