The sudo binary doesn't have an setuid bit that it needs to be useful.
Could be because of the pcap wrappers merge.
Install sudo, try to run it.
It was just a broken env. Sorry to bother you.
nix-user-chroot breaks sudo for instance with the same error message. There might a fix for that, but I have not yet looked into it.
@pstn's occurence was due to the setuid sudo binary being moved from /run/setuid-wrappers to /run/wrappers/bin and his PATH not yet being updated. I'll add a temporary symlink before the release.
I was bit by this and was very confused for some time, but it turns out that the PATH was being overwritten by ~/.zshenv. With that line deleted and a reboot, everything works.
So if you're a zsh user bit by this bug, please check both your .zshrc and .zshenv for any lines setting PATH, and remove them.
Let's keep this issue open until the temporary symlink is added so this isn't forgotten.
What's the symlink fix? I'd like to get sudo working again without waiting.
The idea of the symlink fix is just to make /var/setuid-wrappers a symlink to /run/wrappers/bin
Ohhh, I tried /run/setuid-wrappers (from earlier in the thread), not /var/setuid-wrappers.
I upgraded from 17.03 to 18.03 and I have this problem.
The idea of the symlink fix is just to make
/var/setuid-wrappersa symlink to/run/wrappers/bin
This did not help.
Most helpful comment
@pstn's occurence was due to the setuid sudo binary being moved from
/run/setuid-wrappersto/run/wrappers/binand his PATH not yet being updated. I'll add a temporary symlink before the release.