I'm confused.
Definitely I did not add myself to wheel just now, whether it was default from the start or I'm an idiot and forgot about adding myself to wheel in the past is irrelevant, but since I'm quite sure I must have been in wheel before this sudo issue, how comes I got the error in the first place?
I surmise the sudo upgrade must have changed sudoers permissions. When I gave the guest root privledges I could do root stuff in that account and so I re-enrolled arthur account into the wheel group. I also rebooted after for good measure and all seems normal. I dont know enough to fix sudo stuff though. Sorry. I should add I used settings to give the guest account admin powers. This trick worked 4 years ago and still worked again for me now.
Duh, it didn't occur me it could have been the update. Off I go chasing rabbits once again...
edit: confusion intensifies. I could not find anything in https://archive.archlinux.org/packages/s/sudo/sudo-1.9.9-1-x86_64.pkg.tar.zst that would add me to wheel. Assuming I'm looking at the right package and not missing something. Oh well. My biological system wants to hibernate over low battery.
See you next time and thanks for finding out about the 1.9.8 / 1.9.9 thing.
I'm getting this error too but I can't use sudo at all since it's not accepting my password. I use the same password on all my systems (I know it's dumb but it's to avoid situations like this where I'm locked out) now I can't stay without logging out because if I do, I lose all my Linux system files.
The stinging irony of this whole thing is it's darn near impossible to fix since downgrade requires sudo to be working properly. Snapshots it is... I wish that didn't have to be the answer.
EDIT: And now KDE authentication prompts aren't accepting my password. Has my machine been compromised?
Same issue. I thought I was compromised. Rebooted and sudo worked fine. The same error/warning shows:
[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-runni
ng commands to keep executing.
@teygah@Aegon@ira787@fieldsfury (edit: sorry fieldsfury I didn't see you before )
Only thing that totally got rid of the annoyance for me was to
[sudo]
disabled = true
in ~/.config/starship.toml, which you don't need sudo to edit.
Downgrading a package (like I tried before) is almost always a mess here, better then to use snapper/timeshift to restore the system to before the sudo 1.9.9 update.
sudo should work fine in a shell without starship, just type bash at the command line (assuming you did not configure bash to use starship).