SUMMARY *** yesterday i downloaded kde neon and installed it on an existing windows install by formatting a partition. the software installed perfectly but i had to install a driver and i got https://askubuntu.com/questions/452860/usr-bin-sudo-must-be-owned-by-uid-0-and-have-the-setuid-bit-set /usr/bin/sudo must be owned by uid 0 and have the setuid bit set error. i have tried to find any reason for this but gotten nothing. tried to update the system but that failed because dpkg --configure -a also does not work in installing updates. i tried to reinstall neon on the same partition but that is also refusing to format the drive. i tried to use partition manager in live session but that errored out into setting a new partition on that. i do not want to nuke the entire drive because the other partitions have data that i do not have backup of. i did set "log in automatically" at the user on install script if that helps. also, during install, i set the partition to "/" and left everything else as is. don't know why it broke by itself *** i also dont know which component of plasma to tag so i put plasmashell-general STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Can you clarify what the problem is? You accidentally ran `sudo chown [username] -hR /`? It sounds like this is either a packaging issue in Neon or else user error; moving to Neon for now.
no. i installed a fresh install and had to run sudo ./install.sh, this error came up. also found that i could do no sudo commands so updtes failed to install also
Can you paste the contents of that install script? I suspect it is faulty and blew up your system. In general running random scripts with root permissions ins an incredibly dangerous thing to do and you should avoid it at all costs. If it is unavoidable, you should read the script contents first and make sure you understand what it's going to do. If you are not capable of understanding what it's going to do, you shouldn't run it and should seek out an alternative safer means of installing the software, optimally by getting it from your distro's package repos.
https://bpa.st/NH7Q https://nuevotechindustries.com/download-drivers/ FT-0828_April 2020 onwards https://drive.google.com/uc?export=download&id=1YhYo5u9Pee56IwtR3_wLuTD3qAfAZeA8 this is just drivers for a wifi dongle. i am not sure if the script even ran
I thought you said you ran that script with `sudo`. Did you do that or not? What was the last thing you did before the issue you're reporting started to happen?
yes that is what i said. i copied over the files and ran sudo ./install.sh. nothing before that, it was a fresh install without internet so i wanted to get wifi working, maybe ran ./install.sh without which complained about sudo i tried that? probably
In that case it seems quite clear that something in the install script messed up your system. This is why in general it's strongly recommended to install software using your distro's package manager, Snap, Flatpak, etc. Scripts downloaded from the internet and run as root are indicative of sloppy and amateurish engineering on the part of whoever provided them, so unfortunately I'm not terribly surprised that this one blew up your system. You should report this to whoever you got that script from.