Sudo command Time-out

received sudo 1.9.9.2 now, no more starship error

4 Likes

I just disabled sudo form getting update. I think I will do after it is fixed.

I paused update for sudo. Once the bug is fixed I will update. It is working for me.

I am also reporting this issue. I just did a system update on my 1 month old garuda system and now firing up terminal leads to

[WARN] - (starship::utils): Executing command "/usr/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.

I have not customized the terminal at all.

I experienced this after reinstalling Garuda as I grew out of what I originally partitioned, and wasn't sure I was going to daily drive.

I solved my sudo problem by using su to get root privileges, and used passwd to reset my user passwd, this got me back sudo

I fixed the starship error in terminal start by adding the timeout string suggested above. Hope this helps.

1 Like

Nvm doesn’t work anymore. I have no idea why it did briefly

1 Like

I updated to the Git version of sudo and that fixed it.

2 Likes

Great news

1.9.9.2 is inching closer.

3 Likes

1.9.9.2 shows up now for me when I view system updates!

2 Likes

Since it is solved since post #63 I close here now.