Update Common Problems with startship [WARN] command timeout error

dwilliam62 2024-02-10 22:45:46 +00:00
parent 33af94b7ee
commit 9072d72377

@ -16,10 +16,18 @@ This error is caused by installing using MBR and not UEFI. It is important to us
This can happen after updates. Don't freak out, you just need to reboot so the headers can be reloaded.
## Waybar does not load after a flake-rebuild
## Waybar does not load after a flake-rebuild
This issue can be caused by setting a waybar style value to an invalid value. As of the time of this writing, there are two options in the options.nix file. style1 and style2 If you set that value to anything else waybar will not run, nor will the waybar configuration be installed
This issue can be caused by setting a waybar style value to an invalid value. As of the time of this writing, there are two options in the options.nix file. style1 and style2 If you set that value to anything else waybar will not run, nor will the waybar configuration be installed
waybarStyle = "style1"; # can be style1-2
Resolution: Edit zaneyos/options.nix file, set the correct value and use the flake-rebuild alias.
Resolution: Edit zaneyos/options.nix file, set the correct value and use the flake-rebuild alias.
## \[WARN\] - (starship::utils): Executing command "/run/wrappers/bin/_XXXX_" timed out.
\[WARN\] - (starship::utils): Executing command "/run/wrappers/bin/sudo" timed out. \[WARN\] - (starship::utils): You can set command_timeout in your config to a higher value to allow longer-running commands to keep executing.
Using sudo, or changing into a directory with a GIT repository are common ways this error is generated. You can extend the command timeout in the \~/zaneyos/config/home/files/starship.toml Add command_timeout = 1000 at the top of the file. Then rebuild ZaneyOS 'flake-rebuild'
##