Permissions are broken even after a fresh installHelp recovering broken OS (permissions issue)How to get rid...

Symmetry in quantum mechanics

Re-submission of rejected manuscript without informing co-authors

How to answer pointed "are you quitting" questioning when I don't want them to suspect

Why doesn't a const reference extend the life of a temporary object passed via a function?

Why did the Germans forbid the possession of pet pigeons in Rostov-on-Don in 1941?

Is there a name of the flying bionic bird?

How would photo IDs work for shapeshifters?

Ideas for 3rd eye abilities

Manga about a female worker who got dragged into another world together with this high school girl and she was just told she's not needed anymore

Information to fellow intern about hiring?

Calculate Levenshtein distance between two strings in Python

A poker game description that does not feel gimmicky

What does "enim et" mean?

What does 'script /dev/null' do?

Doomsday-clock for my fantasy planet

What happens when a metallic dragon and a chromatic dragon mate?

Why airport relocation isn't done gradually?

"listening to me about as much as you're listening to this pole here"

When blogging recipes, how can I support both readers who want the narrative/journey and ones who want the printer-friendly recipe?

Landlord wants to switch my lease to a "Land contract" to "get back at the city"

Why is the design of haulage companies so “special”?

Pristine Bit Checking

How is it possible for user's password to be changed after storage was encrypted? (on OS X, Android)

Need help identifying/translating a plaque in Tangier, Morocco



Permissions are broken even after a fresh install


Help recovering broken OS (permissions issue)How to get rid off - sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner sudo: fatal error, unable to load pluginsno Terminal commands are working at all after install of Lubuntu 14.04Not able to change /usr/bin permission - Permission deniedDeleted my /usr/ directory, recovered with chroot now getting a Segmentation fault (core dumped) trying to run SudoUnable to use sudo command/usr/bin/sudo must be owned by uid 0Not able to sudoHow to add /usr/bin to path after I mistakenly removed it (sudo and nano are no longer in path)Another upgrade error Systemd-shim






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















So I decided to install Lubuntu today (it's the 18.04 release with the silly beaver) on my old Asus laptop using an external HDD with a Windows bootloader booting an ISO from disk to launch the live system and install Lubuntu. The install went swimmingly, but the very first thing I try to execute (sudo) gives me this error:



/usr/bin/sudo must be owned by uid 0 and have the setuid bit set [duplicate]


I know this error has been posted more times than I've been around the sun, but whatever I do, whatever I try, nothing remedies it. I tried the permission tricks such as:



chown root:root /usr/bin/sudo && chmod 4755 /usr/bin/sudo


only to have crap thrown in my face yet again, despite me executing this from the root recovery console.
Not only this, but I keep getting permission errors randomly. For example, I try to install a package and I get this random error about permissions on a file in /usr/lib (don't quote me on that) which also complains about invalid permissions.



Eventually, I got the time to do a reinstall, and the exact same issue occurs. So I redownloaded Lubuntu and tried again, only to have the exact same thing happen again.



To be noted: I cannot get online whilst in Lubuntu because I can't install the Atheros drivers due to this fault, so I can't do things like apt-get unless I physically connect my modem into the wall, so that's out of the question.



I verified the ISO and there's no issue there, so I'm lost as to what the cause could be.



Any, and I mean ANY suggestions gladly appreciated.










share|improve this question









New contributor




Melon Chickens is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • You haven't told us what release of Lubuntu you are referring to. I also get the feeling you are talking about a VM installation (not real hardware). Did you verify your download? and then install media? prior to install. You weren't specific about atheros and I don't know what wiki (help.ubuntu.com/community/WifiDocs/Driver/Atheros etc) or online searches & questions on this site you tried to fix so I'll skip that. You also list chown root:root which won't work as listed unless you're logged in as root. You're heavy on story & light on detail in my opinion.

    – guiverc
    5 hours ago











  • Sorry for the ambiguity. Hopefully the post is a bit better now. I am using real hardware and not a virtual machine. You can ignore the part about Atheros for now since it's not part of the issue.

    – Melon Chickens
    5 hours ago











  • To be noted; I did run chown root:root as a root user, since that's what the terminal prompt in the recovery mode uses. The command did not give any verbose output so I assumed it executed fine.

    – Melon Chickens
    4 hours ago











  • "only to have crap thrown in my face yet again" isn't very helpful - if there were error messages, please include them verbatim

    – steeldriver
    3 hours ago


















0















So I decided to install Lubuntu today (it's the 18.04 release with the silly beaver) on my old Asus laptop using an external HDD with a Windows bootloader booting an ISO from disk to launch the live system and install Lubuntu. The install went swimmingly, but the very first thing I try to execute (sudo) gives me this error:



/usr/bin/sudo must be owned by uid 0 and have the setuid bit set [duplicate]


I know this error has been posted more times than I've been around the sun, but whatever I do, whatever I try, nothing remedies it. I tried the permission tricks such as:



chown root:root /usr/bin/sudo && chmod 4755 /usr/bin/sudo


only to have crap thrown in my face yet again, despite me executing this from the root recovery console.
Not only this, but I keep getting permission errors randomly. For example, I try to install a package and I get this random error about permissions on a file in /usr/lib (don't quote me on that) which also complains about invalid permissions.



Eventually, I got the time to do a reinstall, and the exact same issue occurs. So I redownloaded Lubuntu and tried again, only to have the exact same thing happen again.



To be noted: I cannot get online whilst in Lubuntu because I can't install the Atheros drivers due to this fault, so I can't do things like apt-get unless I physically connect my modem into the wall, so that's out of the question.



I verified the ISO and there's no issue there, so I'm lost as to what the cause could be.



Any, and I mean ANY suggestions gladly appreciated.










share|improve this question









New contributor




Melon Chickens is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • You haven't told us what release of Lubuntu you are referring to. I also get the feeling you are talking about a VM installation (not real hardware). Did you verify your download? and then install media? prior to install. You weren't specific about atheros and I don't know what wiki (help.ubuntu.com/community/WifiDocs/Driver/Atheros etc) or online searches & questions on this site you tried to fix so I'll skip that. You also list chown root:root which won't work as listed unless you're logged in as root. You're heavy on story & light on detail in my opinion.

    – guiverc
    5 hours ago











  • Sorry for the ambiguity. Hopefully the post is a bit better now. I am using real hardware and not a virtual machine. You can ignore the part about Atheros for now since it's not part of the issue.

    – Melon Chickens
    5 hours ago











  • To be noted; I did run chown root:root as a root user, since that's what the terminal prompt in the recovery mode uses. The command did not give any verbose output so I assumed it executed fine.

    – Melon Chickens
    4 hours ago











  • "only to have crap thrown in my face yet again" isn't very helpful - if there were error messages, please include them verbatim

    – steeldriver
    3 hours ago














0












0








0








So I decided to install Lubuntu today (it's the 18.04 release with the silly beaver) on my old Asus laptop using an external HDD with a Windows bootloader booting an ISO from disk to launch the live system and install Lubuntu. The install went swimmingly, but the very first thing I try to execute (sudo) gives me this error:



/usr/bin/sudo must be owned by uid 0 and have the setuid bit set [duplicate]


I know this error has been posted more times than I've been around the sun, but whatever I do, whatever I try, nothing remedies it. I tried the permission tricks such as:



chown root:root /usr/bin/sudo && chmod 4755 /usr/bin/sudo


only to have crap thrown in my face yet again, despite me executing this from the root recovery console.
Not only this, but I keep getting permission errors randomly. For example, I try to install a package and I get this random error about permissions on a file in /usr/lib (don't quote me on that) which also complains about invalid permissions.



Eventually, I got the time to do a reinstall, and the exact same issue occurs. So I redownloaded Lubuntu and tried again, only to have the exact same thing happen again.



To be noted: I cannot get online whilst in Lubuntu because I can't install the Atheros drivers due to this fault, so I can't do things like apt-get unless I physically connect my modem into the wall, so that's out of the question.



I verified the ISO and there's no issue there, so I'm lost as to what the cause could be.



Any, and I mean ANY suggestions gladly appreciated.










share|improve this question









New contributor




Melon Chickens is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












So I decided to install Lubuntu today (it's the 18.04 release with the silly beaver) on my old Asus laptop using an external HDD with a Windows bootloader booting an ISO from disk to launch the live system and install Lubuntu. The install went swimmingly, but the very first thing I try to execute (sudo) gives me this error:



/usr/bin/sudo must be owned by uid 0 and have the setuid bit set [duplicate]


I know this error has been posted more times than I've been around the sun, but whatever I do, whatever I try, nothing remedies it. I tried the permission tricks such as:



chown root:root /usr/bin/sudo && chmod 4755 /usr/bin/sudo


only to have crap thrown in my face yet again, despite me executing this from the root recovery console.
Not only this, but I keep getting permission errors randomly. For example, I try to install a package and I get this random error about permissions on a file in /usr/lib (don't quote me on that) which also complains about invalid permissions.



Eventually, I got the time to do a reinstall, and the exact same issue occurs. So I redownloaded Lubuntu and tried again, only to have the exact same thing happen again.



To be noted: I cannot get online whilst in Lubuntu because I can't install the Atheros drivers due to this fault, so I can't do things like apt-get unless I physically connect my modem into the wall, so that's out of the question.



I verified the ISO and there's no issue there, so I'm lost as to what the cause could be.



Any, and I mean ANY suggestions gladly appreciated.







permissions lubuntu sudo






share|improve this question









New contributor




Melon Chickens is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




Melon Chickens is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 4 hours ago







Melon Chickens













New contributor




Melon Chickens is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 5 hours ago









Melon ChickensMelon Chickens

11




11




New contributor




Melon Chickens is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Melon Chickens is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Melon Chickens is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • You haven't told us what release of Lubuntu you are referring to. I also get the feeling you are talking about a VM installation (not real hardware). Did you verify your download? and then install media? prior to install. You weren't specific about atheros and I don't know what wiki (help.ubuntu.com/community/WifiDocs/Driver/Atheros etc) or online searches & questions on this site you tried to fix so I'll skip that. You also list chown root:root which won't work as listed unless you're logged in as root. You're heavy on story & light on detail in my opinion.

    – guiverc
    5 hours ago











  • Sorry for the ambiguity. Hopefully the post is a bit better now. I am using real hardware and not a virtual machine. You can ignore the part about Atheros for now since it's not part of the issue.

    – Melon Chickens
    5 hours ago











  • To be noted; I did run chown root:root as a root user, since that's what the terminal prompt in the recovery mode uses. The command did not give any verbose output so I assumed it executed fine.

    – Melon Chickens
    4 hours ago











  • "only to have crap thrown in my face yet again" isn't very helpful - if there were error messages, please include them verbatim

    – steeldriver
    3 hours ago



















  • You haven't told us what release of Lubuntu you are referring to. I also get the feeling you are talking about a VM installation (not real hardware). Did you verify your download? and then install media? prior to install. You weren't specific about atheros and I don't know what wiki (help.ubuntu.com/community/WifiDocs/Driver/Atheros etc) or online searches & questions on this site you tried to fix so I'll skip that. You also list chown root:root which won't work as listed unless you're logged in as root. You're heavy on story & light on detail in my opinion.

    – guiverc
    5 hours ago











  • Sorry for the ambiguity. Hopefully the post is a bit better now. I am using real hardware and not a virtual machine. You can ignore the part about Atheros for now since it's not part of the issue.

    – Melon Chickens
    5 hours ago











  • To be noted; I did run chown root:root as a root user, since that's what the terminal prompt in the recovery mode uses. The command did not give any verbose output so I assumed it executed fine.

    – Melon Chickens
    4 hours ago











  • "only to have crap thrown in my face yet again" isn't very helpful - if there were error messages, please include them verbatim

    – steeldriver
    3 hours ago

















You haven't told us what release of Lubuntu you are referring to. I also get the feeling you are talking about a VM installation (not real hardware). Did you verify your download? and then install media? prior to install. You weren't specific about atheros and I don't know what wiki (help.ubuntu.com/community/WifiDocs/Driver/Atheros etc) or online searches & questions on this site you tried to fix so I'll skip that. You also list chown root:root which won't work as listed unless you're logged in as root. You're heavy on story & light on detail in my opinion.

– guiverc
5 hours ago





You haven't told us what release of Lubuntu you are referring to. I also get the feeling you are talking about a VM installation (not real hardware). Did you verify your download? and then install media? prior to install. You weren't specific about atheros and I don't know what wiki (help.ubuntu.com/community/WifiDocs/Driver/Atheros etc) or online searches & questions on this site you tried to fix so I'll skip that. You also list chown root:root which won't work as listed unless you're logged in as root. You're heavy on story & light on detail in my opinion.

– guiverc
5 hours ago













Sorry for the ambiguity. Hopefully the post is a bit better now. I am using real hardware and not a virtual machine. You can ignore the part about Atheros for now since it's not part of the issue.

– Melon Chickens
5 hours ago





Sorry for the ambiguity. Hopefully the post is a bit better now. I am using real hardware and not a virtual machine. You can ignore the part about Atheros for now since it's not part of the issue.

– Melon Chickens
5 hours ago













To be noted; I did run chown root:root as a root user, since that's what the terminal prompt in the recovery mode uses. The command did not give any verbose output so I assumed it executed fine.

– Melon Chickens
4 hours ago





To be noted; I did run chown root:root as a root user, since that's what the terminal prompt in the recovery mode uses. The command did not give any verbose output so I assumed it executed fine.

– Melon Chickens
4 hours ago













"only to have crap thrown in my face yet again" isn't very helpful - if there were error messages, please include them verbatim

– steeldriver
3 hours ago





"only to have crap thrown in my face yet again" isn't very helpful - if there were error messages, please include them verbatim

– steeldriver
3 hours ago










0






active

oldest

votes












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






Melon Chickens is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1132284%2fpermissions-are-broken-even-after-a-fresh-install%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes








Melon Chickens is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















Melon Chickens is a new contributor. Be nice, and check out our Code of Conduct.













Melon Chickens is a new contributor. Be nice, and check out our Code of Conduct.












Melon Chickens is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1132284%2fpermissions-are-broken-even-after-a-fresh-install%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Why do type traits not work with types in namespace scope?What are POD types in C++?Why can templates only be...

Will tsunami waves travel forever if there was no land?Why do tsunami waves begin with the water flowing away...

Simple Scan not detecting my scanner (Brother DCP-7055W)Brother MFC-L2700DW printer can print, can't...