“bash: /usr/bin/ls: Permission denied” Arch linux












1















Today I discovered that the command ls to list files, only returns the error:



bash: /usr/bin/ls: Permission denied


This happens for every directory I try and also when running the command as root. The alternative command 'dir' works without any problem.



It may be possible that the problem has started after messing around with libc symlinks last week. I've already removed them and and replaced them with the ones from my live USB stick, so this shouldn't be the problem anymore.



To which package does the ls command belong to and can it just be reinstalled using pacman?










share|improve this question







New contributor




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

























    1















    Today I discovered that the command ls to list files, only returns the error:



    bash: /usr/bin/ls: Permission denied


    This happens for every directory I try and also when running the command as root. The alternative command 'dir' works without any problem.



    It may be possible that the problem has started after messing around with libc symlinks last week. I've already removed them and and replaced them with the ones from my live USB stick, so this shouldn't be the problem anymore.



    To which package does the ls command belong to and can it just be reinstalled using pacman?










    share|improve this question







    New contributor




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























      1












      1








      1








      Today I discovered that the command ls to list files, only returns the error:



      bash: /usr/bin/ls: Permission denied


      This happens for every directory I try and also when running the command as root. The alternative command 'dir' works without any problem.



      It may be possible that the problem has started after messing around with libc symlinks last week. I've already removed them and and replaced them with the ones from my live USB stick, so this shouldn't be the problem anymore.



      To which package does the ls command belong to and can it just be reinstalled using pacman?










      share|improve this question







      New contributor




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












      Today I discovered that the command ls to list files, only returns the error:



      bash: /usr/bin/ls: Permission denied


      This happens for every directory I try and also when running the command as root. The alternative command 'dir' works without any problem.



      It may be possible that the problem has started after messing around with libc symlinks last week. I've already removed them and and replaced them with the ones from my live USB stick, so this shouldn't be the problem anymore.



      To which package does the ls command belong to and can it just be reinstalled using pacman?







      shell ls






      share|improve this question







      New contributor




      Reinout 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




      Reinout 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






      New contributor




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









      asked 9 hours ago









      ReinoutReinout

      61




      61




      New contributor




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





      New contributor





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






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






















          1 Answer
          1






          active

          oldest

          votes


















          0














          I fixed it after reinstalling the coreutils,



          sudo pacman -S coreutils





          share|improve this answer








          New contributor




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
















          • 2





            That would fix ls and the other coreutils tools. If you ran a chmod across the whole /usr/bin, then there are potentially other tools that also have the wrong permissions.

            – Kusalananda
            7 hours ago











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          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: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          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
          });


          }
          });






          Reinout 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%2funix.stackexchange.com%2fquestions%2f505325%2fbash-usr-bin-ls-permission-denied-arch-linux%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














          I fixed it after reinstalling the coreutils,



          sudo pacman -S coreutils





          share|improve this answer








          New contributor




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
















          • 2





            That would fix ls and the other coreutils tools. If you ran a chmod across the whole /usr/bin, then there are potentially other tools that also have the wrong permissions.

            – Kusalananda
            7 hours ago
















          0














          I fixed it after reinstalling the coreutils,



          sudo pacman -S coreutils





          share|improve this answer








          New contributor




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
















          • 2





            That would fix ls and the other coreutils tools. If you ran a chmod across the whole /usr/bin, then there are potentially other tools that also have the wrong permissions.

            – Kusalananda
            7 hours ago














          0












          0








          0







          I fixed it after reinstalling the coreutils,



          sudo pacman -S coreutils





          share|improve this answer








          New contributor




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










          I fixed it after reinstalling the coreutils,



          sudo pacman -S coreutils






          share|improve this answer








          New contributor




          Reinout 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 answer



          share|improve this answer






          New contributor




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









          answered 9 hours ago









          ReinoutReinout

          61




          61




          New contributor




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





          New contributor





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






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








          • 2





            That would fix ls and the other coreutils tools. If you ran a chmod across the whole /usr/bin, then there are potentially other tools that also have the wrong permissions.

            – Kusalananda
            7 hours ago














          • 2





            That would fix ls and the other coreutils tools. If you ran a chmod across the whole /usr/bin, then there are potentially other tools that also have the wrong permissions.

            – Kusalananda
            7 hours ago








          2




          2





          That would fix ls and the other coreutils tools. If you ran a chmod across the whole /usr/bin, then there are potentially other tools that also have the wrong permissions.

          – Kusalananda
          7 hours ago





          That would fix ls and the other coreutils tools. If you ran a chmod across the whole /usr/bin, then there are potentially other tools that also have the wrong permissions.

          – Kusalananda
          7 hours ago










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










          draft saved

          draft discarded


















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













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












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
















          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • 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%2funix.stackexchange.com%2fquestions%2f505325%2fbash-usr-bin-ls-permission-denied-arch-linux%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

          Histoire des bourses de valeurs

          Why is there Russian traffic in my log files?

          Rename multiple files to decrement number in file name?