I recently made a mistake by accidentally updating system packages through pacman and I didn't use Omarchy update. After rebooting the system fails to boot and lands me on some kind of default login screen by the desktop environment. After a couple hours of troubleshooting I eventually restored to snapshot, ran omarchy-update, and manual fixed hyperland configs that needed altered syntax. All of that has gone well enough, but I still have this issue where none of the omarchy-* bin files are installed system wide. While I could hack and make these available via cp or symlink or something I'm worried there are other, more sublte, ways my system is only partially upgraded. I can't seem to get the system to fix the installation through any of the scripts currently here nor can I track down which part of the process either installs these commands system wide or updates PATH so they are visible. Any help would be much appreciated. Oddly enough, there has always been 1 omarchy bin available system wide and it's omarchy-nvim-setup. That is the only one in /usr/bin and even more peculiar that one is not found in ~/.local/share/omarchy/bin.
#Help correcting failed upgrade to 3.3.x all omarchy bin are missing from system install location
graceful comet
In case this sheds additional light on the situation, I see the same login screen in this post: https://discord.com/channels/1390012484194275541/1461470469424418947. I was able to figure out that I can either boot to TTY or change the session to Hyprland to get in.
I suspect that the reason I end up at this screen to begin with after successfully logging into the expected Omarchy login screen is because one or more omarch-* commands fail due to not being available from PATH. So I think these two issues are probably one and the same
graceful comet
I may have found that it was NVIDIA drivers. It appears the ./install/config/hardware/nvidia.sh script may have partially executed. I'm now going through every install config script and running it if needed
graceful comet
I'm unsure if this is an issue in the Omarchy installation scripts but I'm finding that nvidia.sh writes NVIDIA variables to ~/.config/hypr/envs.conf but never updates ~/.config/hypr/hyprland.conf to source that file. So it just seems like a loose appendage. I previously had envs.conf sourced so I'm going to keep that for now unless it causes issues.
For what it's worth, I've been using AI to help me diagnose these issues and understand the configuration for all these tools and services. It seems to believe that those NVIDIA variabes should be loaded earlier in the process. It suggests variable definitions of NVD_BACKEND, LIBVA_DRIVER_NAME, etc... to be in uwsm/env instead of in hyprland configs... I'm not knowledgable enough in the subject to know if that is true. Maybe someone else that reads this and knows can choose to weigh in and integrate a change like that.