From 9e5c521e13cc6d881c3cedda8bd9f387db0e4399 Mon Sep 17 00:00:00 2001
From: "John D. Baker" <jdbaker@consolidated.net>
Date: Sun, 18 Jun 2023 20:11:31 +0200
Subject: Disable SIGALRM before launching other WMs

Via 43bdf499, `alarm(2)` might get issued which might trigger a SIGALRM
in some edge cases in a shutdown / restart scenario. In case of a
restart-to-other-WM scenario, this will yield a SIGALRM in the other WM
which then might fail because no SIGALRM handler is installed.

This commit addresses the issue by disabling any alarm to our own
instance before launching the other WM.
---
 src/main.cc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/main.cc b/src/main.cc
index 574020a..8d78325 100644
--- a/src/main.cc
+++ b/src/main.cc
@@ -266,6 +266,7 @@ int main(int argc, char **argv) {
     FbTk::FbStringUtil::shutdown();
 
     if (restarting) {
+        alarm(0);
         if (!restart_argument.empty()) {
             const char *shell = getenv("SHELL");
             if (!shell)
-- 
cgit v0.11.2