From bcfade3e24208f631bbc353135df3d58beac002f Mon Sep 17 00:00:00 2001 From: Don Williams Date: Fri, 14 Nov 2025 00:31:38 -0500 Subject: [PATCH] Checking for install triggered broken ags to start On branch development Your branch is up to date with 'origin/development'. Changes to be committed: modified: install-scripts/ags.sh --- install-scripts/ags.sh | 13 +++---------- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/install-scripts/ags.sh b/install-scripts/ags.sh index ab2de50..d86175c 100755 --- a/install-scripts/ags.sh +++ b/install-scripts/ags.sh @@ -45,16 +45,9 @@ set -eo pipefail LOG="Install-Logs/install-$(date +%d-%H%M%S)_ags.log" MLOG="install-$(date +%d-%H%M%S)_ags2.log" -# Check if AGS is installed -if command -v ags &>/dev/null; then - AGS_VERSION=$(ags -v | awk '{print $NF}') - if [[ "$AGS_VERSION" == "1.9.0" ]]; then - printf "${INFO} ${MAGENTA}Aylur's GTK Shell v1.9.0${RESET} is already installed. Skipping installation." - printf "\n%.0s" {1..2} - exit 0 - fi -fi - +# NOTE: We intentionally do NOT run `ags -v` here, because a broken AGS +# installation (missing GUtils, etc.) would crash gjs and spam errors +# during install. We always (re)install v1.9.0 when this script is run. # Installation of main components printf "\n%s - Installing ${SKY_BLUE}Aylur's GTK shell $ags_tag${RESET} Dependencies \n" "${NOTE}"