From bc47021c3bb98a207b93a9b15f233b312fce5252 Mon Sep 17 00:00:00 2001 From: "Fred T. Hamster" Date: Sun, 30 Nov 2025 18:29:45 -0500 Subject: [PATCH] made the xss startup not errorful there are too many things that can seem to go wrong with the xss-lock startup, but which leave it in a still functional state, so we made the error check after running it allow continuation. --- scripts/core/start_xwin_screensaver.sh | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/scripts/core/start_xwin_screensaver.sh b/scripts/core/start_xwin_screensaver.sh index 45a71750..b47de630 100644 --- a/scripts/core/start_xwin_screensaver.sh +++ b/scripts/core/start_xwin_screensaver.sh @@ -5,6 +5,7 @@ source "$FEISTY_MEOW_SCRIPTS/core/functions.sh" source "$FEISTY_MEOW_SCRIPTS/processes/process_manager.sh" +source "$FEISTY_MEOW_SCRIPTS/tty/terminal_titler.sh" if ! test_for_xwin; then if [ ! -z "$DEBUG_FEISTY_MEOW" ]; then @@ -52,6 +53,9 @@ if [ $? -eq 0 ]; then # code borrowed from replace_pattern_in_file, but we need sudo here. sudo sed -i -e "s%$pattern%$replacement%g" "$file" exit_on_error "editing the xsecurelock saver_xscreensaver file" + if [ ! -z "$DEBUG_FEISTY_MEOW" ]; then + echo "successfully modified the saver_xscreensaver file for xsecurelock" + fi fi DIMMER="/usr/libexec/xsecurelock/dimmer" @@ -67,7 +71,7 @@ exit_on_error "setting the x window inactivity timeout" start_background_action \ "xss-lock -n "$DIMMER" -l -- xsecurelock" -exit_on_error "installing xsecurelock as the screensaver" +continue_on_error "starting up xsecurelock as the screensaver" if [ ! -z "$DEBUG_FEISTY_MEOW" ]; then echo xsecurelock has been started. -- 2.34.1