aboutsummaryrefslogtreecommitdiff
path: root/sway/config
diff options
context:
space:
mode:
authorTamino Bauknecht <dev@tb6.eu>2023-12-12 22:54:31 +0100
committerSimon Ser <contact@emersion.fr>2024-01-29 14:12:39 +0100
commitc8676fad54bb0f4152947a6781626872bfa6ad64 (patch)
treeeeb76f1fe675424703eed79b97325af23b355d62 /sway/config
parente39b0b816b8fe58a8c8e0ca1c0082c5065d444cc (diff)
sway/output: Improve logging of swaybg execvp failure and more checks
This doesn't catch the error if a background changing command is executed via swaymsg, but improves logging. The additional checks at least propagate if e.g. forking failed.
Diffstat (limited to 'sway/config')
-rw-r--r--sway/config/output.c9
1 files changed, 6 insertions, 3 deletions
diff --git a/sway/config/output.c b/sway/config/output.c
index 1a5215fe..54ebaa17 100644
--- a/sway/config/output.c
+++ b/sway/config/output.c
@@ -822,7 +822,9 @@ static bool _spawn_swaybg(char **command) {
setenv("WAYLAND_SOCKET", wayland_socket_str, true);
execvp(command[0], command);
- sway_log_errno(SWAY_ERROR, "execvp failed");
+ sway_log_errno(SWAY_ERROR, "failed to execute '%s' "
+ "(background configuration probably not applied)",
+ command[0]);
_exit(EXIT_FAILURE);
}
_exit(EXIT_SUCCESS);
@@ -832,12 +834,13 @@ static bool _spawn_swaybg(char **command) {
sway_log_errno(SWAY_ERROR, "close failed");
return false;
}
- if (waitpid(pid, NULL, 0) < 0) {
+ int fork_status = 0;
+ if (waitpid(pid, &fork_status, 0) < 0) {
sway_log_errno(SWAY_ERROR, "waitpid failed");
return false;
}
- return true;
+ return WIFEXITED(fork_status) && WEXITSTATUS(fork_status) == EXIT_SUCCESS;
}
bool spawn_swaybg(void) {