Can't access home folder












2














While installing Matlab, I mistakenly typed sudo chmod +x ./java in the home folder.



And I got i/o error that you are not allowed to access the home folder. Suddenly everything in my home folder disappeared.



Although the disk shows filled up data. I guess the folder permission need to be changed.










share|improve this question
























  • first see your home folder permission ls -l.if there have't any execute permission then give permission with 744 or u+x;
    – sohel4r
    Apr 25 '14 at 16:44










  • ls -l does not show anything......should I just type chmod u+x?
    – user274219
    Apr 25 '14 at 16:52






  • 2




    I question your diagnosis. Simply running chmod +x ./java as root will not break access to $HOME. Do ls -ld $HOME;echo $HOME to show $HOME permissions, and to verify $HOME makes sense. My $HOME is mode 0700 (rwx------). sudo chmod u=rwx,g=,o= $HOME is my suggestion. sudo chmod u=rwx,g=rx,o= $HOME to allow group read and search. man chmod
    – waltinator
    Apr 25 '14 at 17:26












  • ls -ld shows:dr-xr-xr-x 10 root root 2048 2011-09-23 21:47
    – user274219
    Apr 25 '14 at 17:36










  • I agree with waltinator. It doesn't make sense for that command to change ownership and remove write permissions. Do you maybe have a wrapper on sudo or chmod? Also you didn't even need to run chmod as root, since I assume you're the file owner. (BTW I realize this is an old post -- just commenting for future readers.)
    – wjandrea
    Dec 15 '17 at 1:28
















2














While installing Matlab, I mistakenly typed sudo chmod +x ./java in the home folder.



And I got i/o error that you are not allowed to access the home folder. Suddenly everything in my home folder disappeared.



Although the disk shows filled up data. I guess the folder permission need to be changed.










share|improve this question
























  • first see your home folder permission ls -l.if there have't any execute permission then give permission with 744 or u+x;
    – sohel4r
    Apr 25 '14 at 16:44










  • ls -l does not show anything......should I just type chmod u+x?
    – user274219
    Apr 25 '14 at 16:52






  • 2




    I question your diagnosis. Simply running chmod +x ./java as root will not break access to $HOME. Do ls -ld $HOME;echo $HOME to show $HOME permissions, and to verify $HOME makes sense. My $HOME is mode 0700 (rwx------). sudo chmod u=rwx,g=,o= $HOME is my suggestion. sudo chmod u=rwx,g=rx,o= $HOME to allow group read and search. man chmod
    – waltinator
    Apr 25 '14 at 17:26












  • ls -ld shows:dr-xr-xr-x 10 root root 2048 2011-09-23 21:47
    – user274219
    Apr 25 '14 at 17:36










  • I agree with waltinator. It doesn't make sense for that command to change ownership and remove write permissions. Do you maybe have a wrapper on sudo or chmod? Also you didn't even need to run chmod as root, since I assume you're the file owner. (BTW I realize this is an old post -- just commenting for future readers.)
    – wjandrea
    Dec 15 '17 at 1:28














2












2








2


0





While installing Matlab, I mistakenly typed sudo chmod +x ./java in the home folder.



And I got i/o error that you are not allowed to access the home folder. Suddenly everything in my home folder disappeared.



Although the disk shows filled up data. I guess the folder permission need to be changed.










share|improve this question















While installing Matlab, I mistakenly typed sudo chmod +x ./java in the home folder.



And I got i/o error that you are not allowed to access the home folder. Suddenly everything in my home folder disappeared.



Although the disk shows filled up data. I guess the folder permission need to be changed.







permissions chmod chown






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 25 '14 at 16:51









Lucio

12.4k2185157




12.4k2185157










asked Apr 25 '14 at 16:36









user274219

1112




1112












  • first see your home folder permission ls -l.if there have't any execute permission then give permission with 744 or u+x;
    – sohel4r
    Apr 25 '14 at 16:44










  • ls -l does not show anything......should I just type chmod u+x?
    – user274219
    Apr 25 '14 at 16:52






  • 2




    I question your diagnosis. Simply running chmod +x ./java as root will not break access to $HOME. Do ls -ld $HOME;echo $HOME to show $HOME permissions, and to verify $HOME makes sense. My $HOME is mode 0700 (rwx------). sudo chmod u=rwx,g=,o= $HOME is my suggestion. sudo chmod u=rwx,g=rx,o= $HOME to allow group read and search. man chmod
    – waltinator
    Apr 25 '14 at 17:26












  • ls -ld shows:dr-xr-xr-x 10 root root 2048 2011-09-23 21:47
    – user274219
    Apr 25 '14 at 17:36










  • I agree with waltinator. It doesn't make sense for that command to change ownership and remove write permissions. Do you maybe have a wrapper on sudo or chmod? Also you didn't even need to run chmod as root, since I assume you're the file owner. (BTW I realize this is an old post -- just commenting for future readers.)
    – wjandrea
    Dec 15 '17 at 1:28


















  • first see your home folder permission ls -l.if there have't any execute permission then give permission with 744 or u+x;
    – sohel4r
    Apr 25 '14 at 16:44










  • ls -l does not show anything......should I just type chmod u+x?
    – user274219
    Apr 25 '14 at 16:52






  • 2




    I question your diagnosis. Simply running chmod +x ./java as root will not break access to $HOME. Do ls -ld $HOME;echo $HOME to show $HOME permissions, and to verify $HOME makes sense. My $HOME is mode 0700 (rwx------). sudo chmod u=rwx,g=,o= $HOME is my suggestion. sudo chmod u=rwx,g=rx,o= $HOME to allow group read and search. man chmod
    – waltinator
    Apr 25 '14 at 17:26












  • ls -ld shows:dr-xr-xr-x 10 root root 2048 2011-09-23 21:47
    – user274219
    Apr 25 '14 at 17:36










  • I agree with waltinator. It doesn't make sense for that command to change ownership and remove write permissions. Do you maybe have a wrapper on sudo or chmod? Also you didn't even need to run chmod as root, since I assume you're the file owner. (BTW I realize this is an old post -- just commenting for future readers.)
    – wjandrea
    Dec 15 '17 at 1:28
















first see your home folder permission ls -l.if there have't any execute permission then give permission with 744 or u+x;
– sohel4r
Apr 25 '14 at 16:44




first see your home folder permission ls -l.if there have't any execute permission then give permission with 744 or u+x;
– sohel4r
Apr 25 '14 at 16:44












ls -l does not show anything......should I just type chmod u+x?
– user274219
Apr 25 '14 at 16:52




ls -l does not show anything......should I just type chmod u+x?
– user274219
Apr 25 '14 at 16:52




2




2




I question your diagnosis. Simply running chmod +x ./java as root will not break access to $HOME. Do ls -ld $HOME;echo $HOME to show $HOME permissions, and to verify $HOME makes sense. My $HOME is mode 0700 (rwx------). sudo chmod u=rwx,g=,o= $HOME is my suggestion. sudo chmod u=rwx,g=rx,o= $HOME to allow group read and search. man chmod
– waltinator
Apr 25 '14 at 17:26






I question your diagnosis. Simply running chmod +x ./java as root will not break access to $HOME. Do ls -ld $HOME;echo $HOME to show $HOME permissions, and to verify $HOME makes sense. My $HOME is mode 0700 (rwx------). sudo chmod u=rwx,g=,o= $HOME is my suggestion. sudo chmod u=rwx,g=rx,o= $HOME to allow group read and search. man chmod
– waltinator
Apr 25 '14 at 17:26














ls -ld shows:dr-xr-xr-x 10 root root 2048 2011-09-23 21:47
– user274219
Apr 25 '14 at 17:36




ls -ld shows:dr-xr-xr-x 10 root root 2048 2011-09-23 21:47
– user274219
Apr 25 '14 at 17:36












I agree with waltinator. It doesn't make sense for that command to change ownership and remove write permissions. Do you maybe have a wrapper on sudo or chmod? Also you didn't even need to run chmod as root, since I assume you're the file owner. (BTW I realize this is an old post -- just commenting for future readers.)
– wjandrea
Dec 15 '17 at 1:28




I agree with waltinator. It doesn't make sense for that command to change ownership and remove write permissions. Do you maybe have a wrapper on sudo or chmod? Also you didn't even need to run chmod as root, since I assume you're the file owner. (BTW I realize this is an old post -- just commenting for future readers.)
– wjandrea
Dec 15 '17 at 1:28










1 Answer
1






active

oldest

votes


















0














You just need to chown the directory back to yourself.



sudo chown -R user /home/user





share|improve this answer





















  • According to the comments, the owner doesn't have write permissions, so OP will also need to run chmod u+w /home/user.
    – wjandrea
    Dec 15 '17 at 1:52












  • And the group ownership was changed to, so instead of just user, use user: in the chown command.
    – wjandrea
    Dec 15 '17 at 1:53










  • Also do you need to make it recursive? Aren't there files in the home folder that are supposed to be owned by root, or am I thinking of something else?
    – wjandrea
    Dec 15 '17 at 1:54











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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f455315%2fcant-access-home-folder%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














You just need to chown the directory back to yourself.



sudo chown -R user /home/user





share|improve this answer





















  • According to the comments, the owner doesn't have write permissions, so OP will also need to run chmod u+w /home/user.
    – wjandrea
    Dec 15 '17 at 1:52












  • And the group ownership was changed to, so instead of just user, use user: in the chown command.
    – wjandrea
    Dec 15 '17 at 1:53










  • Also do you need to make it recursive? Aren't there files in the home folder that are supposed to be owned by root, or am I thinking of something else?
    – wjandrea
    Dec 15 '17 at 1:54
















0














You just need to chown the directory back to yourself.



sudo chown -R user /home/user





share|improve this answer





















  • According to the comments, the owner doesn't have write permissions, so OP will also need to run chmod u+w /home/user.
    – wjandrea
    Dec 15 '17 at 1:52












  • And the group ownership was changed to, so instead of just user, use user: in the chown command.
    – wjandrea
    Dec 15 '17 at 1:53










  • Also do you need to make it recursive? Aren't there files in the home folder that are supposed to be owned by root, or am I thinking of something else?
    – wjandrea
    Dec 15 '17 at 1:54














0












0








0






You just need to chown the directory back to yourself.



sudo chown -R user /home/user





share|improve this answer












You just need to chown the directory back to yourself.



sudo chown -R user /home/user






share|improve this answer












share|improve this answer



share|improve this answer










answered Apr 26 '14 at 1:31









lbaile200

546412




546412












  • According to the comments, the owner doesn't have write permissions, so OP will also need to run chmod u+w /home/user.
    – wjandrea
    Dec 15 '17 at 1:52












  • And the group ownership was changed to, so instead of just user, use user: in the chown command.
    – wjandrea
    Dec 15 '17 at 1:53










  • Also do you need to make it recursive? Aren't there files in the home folder that are supposed to be owned by root, or am I thinking of something else?
    – wjandrea
    Dec 15 '17 at 1:54


















  • According to the comments, the owner doesn't have write permissions, so OP will also need to run chmod u+w /home/user.
    – wjandrea
    Dec 15 '17 at 1:52












  • And the group ownership was changed to, so instead of just user, use user: in the chown command.
    – wjandrea
    Dec 15 '17 at 1:53










  • Also do you need to make it recursive? Aren't there files in the home folder that are supposed to be owned by root, or am I thinking of something else?
    – wjandrea
    Dec 15 '17 at 1:54
















According to the comments, the owner doesn't have write permissions, so OP will also need to run chmod u+w /home/user.
– wjandrea
Dec 15 '17 at 1:52






According to the comments, the owner doesn't have write permissions, so OP will also need to run chmod u+w /home/user.
– wjandrea
Dec 15 '17 at 1:52














And the group ownership was changed to, so instead of just user, use user: in the chown command.
– wjandrea
Dec 15 '17 at 1:53




And the group ownership was changed to, so instead of just user, use user: in the chown command.
– wjandrea
Dec 15 '17 at 1:53












Also do you need to make it recursive? Aren't there files in the home folder that are supposed to be owned by root, or am I thinking of something else?
– wjandrea
Dec 15 '17 at 1:54




Also do you need to make it recursive? Aren't there files in the home folder that are supposed to be owned by root, or am I thinking of something else?
– wjandrea
Dec 15 '17 at 1:54


















draft saved

draft discarded




















































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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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%2f455315%2fcant-access-home-folder%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

Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

ComboBox Display Member on multiple fields

Is it possible to collect Nectar points via Trainline?