hi I can't seem to install anything through pamac or write to disk. getting the following error. not sure how to change the ownership or permission of sudo. I only have one user account that's admin, no guest accounts. not sure how to log in as root as suggested by previous posts on this problem
/usr/bin/sudo must be owned by uid 0 and have the setuid bit set
when I use pamac to download something it says authentication failed
If a file owned by a package changes (or has been changed) then the easiest way to revert it to the default is to reinstall the package.
In this case you'll have to use a different route to get root permissions for installing the package, so either log in to a TTY as root or use su - in a terminal. If you don't have a password set for root then you'll have to use a chroot, How to chroot Garuda Linux.
I logged into root, deleted my all users and their files, I then added a new user as an admin. still having same issue, not able to access anything, authentication failing. the new user opens Garuda Welcome but cannot access Qwikaccess. I'm getting
"error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" usr/lib/sudo/sudoer.so must be owned by uid 0"
I logged into root, opened terminal and tried sudo update but getting same error "must be owned by uid 0"
Not sure why you're using sudo when logged in as root, or why you deleted your user and files, or are trying to update. All I suggested was to reinstall the sudo package, e.g.:
You're getting a permissions error on the executable in a non home directory file. Deleting and recreating users isn't going to change the UID not being set.
Hi. The thing is I accidently changed the root ownership in /usr/bin/ to the active user and I'm trying to give ownership back to root, but I can't make it work. No matter what I try it give me
sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
or
chown: changing ownership of '/usr/bin/sudo': Operation not permitted
This needs to be run as root. Elevate to root with su and try again.
Another option would be to restore a snapshot from before the mistake.
If you need any more help than that, please open a new thread. I'm going to close this one down because it is almost a year old and the original issue was already adequately addressed.