Added myself to sudo group in recovery mode, but still cannot use sudo: “Sorry, try again”












1














This is for an Ubuntu 15.04 on a laptop (Dell inspiron 3135).



Somehow the capability to use sudo got lost, and, probably relatedly, I can no longer log in at the lock screen. There is no problem logging in after a reboot. But I can no longer make software updates if they require root privilege; when trying to authenticate with my user password the dialog window "shakes its head" and the request is denied. So I have to cancel software updates.



Here is what I've tried so far:



Since I obviously can't use sudo for anything I booted the system up in recovery mode and used the <drop to root shell> menu item. Then I get a prompt



root>


I then mount the / partition using



mount -o rw,remount /


And then tried first (let's just say my login is wuzzle)



usermod -a -G sudo wuzzle


Then rebooted, logged on and find that I still couldn't use sudo



Next I tried, after the same procedure as above,



adduser wuzzle sudo


This command, as the previous one, was accepted without response.



Yet, after reboot and login I still can't sudo. For example:



ls -l  /etc/sudoers


shows it has this ownership



-r--r------1 root root


Further, trying



cd /etc/; more sudoers


gives



sudoers permission denied


and



$ sudo more sudoers
[sudo]password for wuzzle: (password entered)
Sorry, try again.


Also, the date of the file /etc/sudoers indicates that it was unchanged even though I used before commands (as root) that I had expected should change the file.



Now I'm out of ideas. I tried to find a solution by searching and browsing around but it appears that everything written about similar problems always gives advice using commands that require sudo. So it's all catch 22.



Later added:



I also tried to use the same commands again (from the root shell in recovery mode):



> adduser wuzzle sudo
The user wuzzle is already a member of `sudo`.


But that's not true.










share|improve this question





























    1














    This is for an Ubuntu 15.04 on a laptop (Dell inspiron 3135).



    Somehow the capability to use sudo got lost, and, probably relatedly, I can no longer log in at the lock screen. There is no problem logging in after a reboot. But I can no longer make software updates if they require root privilege; when trying to authenticate with my user password the dialog window "shakes its head" and the request is denied. So I have to cancel software updates.



    Here is what I've tried so far:



    Since I obviously can't use sudo for anything I booted the system up in recovery mode and used the <drop to root shell> menu item. Then I get a prompt



    root>


    I then mount the / partition using



    mount -o rw,remount /


    And then tried first (let's just say my login is wuzzle)



    usermod -a -G sudo wuzzle


    Then rebooted, logged on and find that I still couldn't use sudo



    Next I tried, after the same procedure as above,



    adduser wuzzle sudo


    This command, as the previous one, was accepted without response.



    Yet, after reboot and login I still can't sudo. For example:



    ls -l  /etc/sudoers


    shows it has this ownership



    -r--r------1 root root


    Further, trying



    cd /etc/; more sudoers


    gives



    sudoers permission denied


    and



    $ sudo more sudoers
    [sudo]password for wuzzle: (password entered)
    Sorry, try again.


    Also, the date of the file /etc/sudoers indicates that it was unchanged even though I used before commands (as root) that I had expected should change the file.



    Now I'm out of ideas. I tried to find a solution by searching and browsing around but it appears that everything written about similar problems always gives advice using commands that require sudo. So it's all catch 22.



    Later added:



    I also tried to use the same commands again (from the root shell in recovery mode):



    > adduser wuzzle sudo
    The user wuzzle is already a member of `sudo`.


    But that's not true.










    share|improve this question



























      1












      1








      1







      This is for an Ubuntu 15.04 on a laptop (Dell inspiron 3135).



      Somehow the capability to use sudo got lost, and, probably relatedly, I can no longer log in at the lock screen. There is no problem logging in after a reboot. But I can no longer make software updates if they require root privilege; when trying to authenticate with my user password the dialog window "shakes its head" and the request is denied. So I have to cancel software updates.



      Here is what I've tried so far:



      Since I obviously can't use sudo for anything I booted the system up in recovery mode and used the <drop to root shell> menu item. Then I get a prompt



      root>


      I then mount the / partition using



      mount -o rw,remount /


      And then tried first (let's just say my login is wuzzle)



      usermod -a -G sudo wuzzle


      Then rebooted, logged on and find that I still couldn't use sudo



      Next I tried, after the same procedure as above,



      adduser wuzzle sudo


      This command, as the previous one, was accepted without response.



      Yet, after reboot and login I still can't sudo. For example:



      ls -l  /etc/sudoers


      shows it has this ownership



      -r--r------1 root root


      Further, trying



      cd /etc/; more sudoers


      gives



      sudoers permission denied


      and



      $ sudo more sudoers
      [sudo]password for wuzzle: (password entered)
      Sorry, try again.


      Also, the date of the file /etc/sudoers indicates that it was unchanged even though I used before commands (as root) that I had expected should change the file.



      Now I'm out of ideas. I tried to find a solution by searching and browsing around but it appears that everything written about similar problems always gives advice using commands that require sudo. So it's all catch 22.



      Later added:



      I also tried to use the same commands again (from the root shell in recovery mode):



      > adduser wuzzle sudo
      The user wuzzle is already a member of `sudo`.


      But that's not true.










      share|improve this question















      This is for an Ubuntu 15.04 on a laptop (Dell inspiron 3135).



      Somehow the capability to use sudo got lost, and, probably relatedly, I can no longer log in at the lock screen. There is no problem logging in after a reboot. But I can no longer make software updates if they require root privilege; when trying to authenticate with my user password the dialog window "shakes its head" and the request is denied. So I have to cancel software updates.



      Here is what I've tried so far:



      Since I obviously can't use sudo for anything I booted the system up in recovery mode and used the <drop to root shell> menu item. Then I get a prompt



      root>


      I then mount the / partition using



      mount -o rw,remount /


      And then tried first (let's just say my login is wuzzle)



      usermod -a -G sudo wuzzle


      Then rebooted, logged on and find that I still couldn't use sudo



      Next I tried, after the same procedure as above,



      adduser wuzzle sudo


      This command, as the previous one, was accepted without response.



      Yet, after reboot and login I still can't sudo. For example:



      ls -l  /etc/sudoers


      shows it has this ownership



      -r--r------1 root root


      Further, trying



      cd /etc/; more sudoers


      gives



      sudoers permission denied


      and



      $ sudo more sudoers
      [sudo]password for wuzzle: (password entered)
      Sorry, try again.


      Also, the date of the file /etc/sudoers indicates that it was unchanged even though I used before commands (as root) that I had expected should change the file.



      Now I'm out of ideas. I tried to find a solution by searching and browsing around but it appears that everything written about similar problems always gives advice using commands that require sudo. So it's all catch 22.



      Later added:



      I also tried to use the same commands again (from the root shell in recovery mode):



      > adduser wuzzle sudo
      The user wuzzle is already a member of `sudo`.


      But that's not true.







      permissions password sudo






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 19 '18 at 20:03









      Zanna

      50.3k13133241




      50.3k13133241










      asked Jun 13 '15 at 2:50









      ReinerReiner

      64




      64






















          2 Answers
          2






          active

          oldest

          votes


















          1














          From your description, the account password itself isn't correct (the dialog window "shakes its head"). If this is the case, resetting your password with the rescue prompt should fix it.






          share|improve this answer





















          • Thank you for this hint. It was not the reason but it lead to finding the reason: Nothing was wrong with sudo, but my keyboard map was messed up (did not notice I was using Japanese keyboard layout the whole time which became default immediately after the window system is fired up. So i could log in initially every time but after that the none letter characters I typed where not the same as what the system received)
            – Reiner
            Jun 13 '15 at 15:37












          • What a beartrap! Glad it is solved.
            – Max Lemieux
            Jun 13 '15 at 17:59



















          1














          As per your comment, the reason for this was that your system was set to a different keyboard layout to the one you expected. I've run into that problem too. The keyboard shortcut to switch layout should work fine at the lock screen.



          I'm mainly writing this answer to correct a few misconceptions in your question.



          Max Lemieux's answer points out that the problem here was that you were typing the wrong password (not because you were making a mistake of course, but because you were typing on the wrong layout and had no way of knowing that because nothing shows up when the password is typed) and that is clear from the error you show:



          $ sudo more sudoers
          [sudo]password for wuzzle: (password entered)
          Sorry, try again.


          This error just means the wrong password was entered.



          You showed in your question your repeated efforts to fix this by adding yourself to the sudo group. You even accused Bash of lying to you when it said you were already in the sudo group(!) The commands you used to add yourself to the sudo group were correct, and you noticed that they returned no errors. If you had not been in the sudo group, this is what would have happened when you tried to use sudo:



          $ sudo uname -r
          [sudo] password for unicorn:
          unicorn is not in the sudoers file. This incident will be reported.


          You could have checked what groups you were in on the command line without needing sudo, using, for example, these commands:



          $ groups
          zanna adm cdrom sudo dip plugdev lpadmin sambashare
          $ id
          uid=1000(zanna) gid=1000(zanna) groups=1000(zanna),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),120(lpadmin),130(sambashare)


          You also said this




          Yet, after reboot and login I still can't sudo. For example:



          ls -l  /etc/sudoers


          shows it has this ownership



          -r--r------1 root root



          That's exactly what it should be, and if those ownerships and those permissions are changed, sudo will refuse to work very stubbornly until they have been fixed (of course you will need to somehow get a root shell to fix it because you won't be able to use sudo). You should never change the permissions of the sudoers file.




          Also, the date of the file /etc/sudoers indicates that it was unchanged even though I used before commands (as root) that I had expected should change the file.




          Adding a user to the sudo group does not change the sudoers file. If you examine the file, you will see how it is that adding a user to the sudo group gives them access to sudo:



          # Allow members of group sudo to execute any command
          %sudo ALL=(ALL:ALL) ALL


          So, no need for a line about each user - this one line plus group membership gives you all the privileges you'll need. As far as I know, the sudoers file is never edited automatically.



          If you ever do need to edit /etc/sudoers, be sure to use sudo visudo which won't let you save the file if you've introduced syntax errors.






          share|improve this answer























            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%2f635836%2fadded-myself-to-sudo-group-in-recovery-mode-but-still-cannot-use-sudo-sorry%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            From your description, the account password itself isn't correct (the dialog window "shakes its head"). If this is the case, resetting your password with the rescue prompt should fix it.






            share|improve this answer





















            • Thank you for this hint. It was not the reason but it lead to finding the reason: Nothing was wrong with sudo, but my keyboard map was messed up (did not notice I was using Japanese keyboard layout the whole time which became default immediately after the window system is fired up. So i could log in initially every time but after that the none letter characters I typed where not the same as what the system received)
              – Reiner
              Jun 13 '15 at 15:37












            • What a beartrap! Glad it is solved.
              – Max Lemieux
              Jun 13 '15 at 17:59
















            1














            From your description, the account password itself isn't correct (the dialog window "shakes its head"). If this is the case, resetting your password with the rescue prompt should fix it.






            share|improve this answer





















            • Thank you for this hint. It was not the reason but it lead to finding the reason: Nothing was wrong with sudo, but my keyboard map was messed up (did not notice I was using Japanese keyboard layout the whole time which became default immediately after the window system is fired up. So i could log in initially every time but after that the none letter characters I typed where not the same as what the system received)
              – Reiner
              Jun 13 '15 at 15:37












            • What a beartrap! Glad it is solved.
              – Max Lemieux
              Jun 13 '15 at 17:59














            1












            1








            1






            From your description, the account password itself isn't correct (the dialog window "shakes its head"). If this is the case, resetting your password with the rescue prompt should fix it.






            share|improve this answer












            From your description, the account password itself isn't correct (the dialog window "shakes its head"). If this is the case, resetting your password with the rescue prompt should fix it.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jun 13 '15 at 3:47









            Max LemieuxMax Lemieux

            1213




            1213












            • Thank you for this hint. It was not the reason but it lead to finding the reason: Nothing was wrong with sudo, but my keyboard map was messed up (did not notice I was using Japanese keyboard layout the whole time which became default immediately after the window system is fired up. So i could log in initially every time but after that the none letter characters I typed where not the same as what the system received)
              – Reiner
              Jun 13 '15 at 15:37












            • What a beartrap! Glad it is solved.
              – Max Lemieux
              Jun 13 '15 at 17:59


















            • Thank you for this hint. It was not the reason but it lead to finding the reason: Nothing was wrong with sudo, but my keyboard map was messed up (did not notice I was using Japanese keyboard layout the whole time which became default immediately after the window system is fired up. So i could log in initially every time but after that the none letter characters I typed where not the same as what the system received)
              – Reiner
              Jun 13 '15 at 15:37












            • What a beartrap! Glad it is solved.
              – Max Lemieux
              Jun 13 '15 at 17:59
















            Thank you for this hint. It was not the reason but it lead to finding the reason: Nothing was wrong with sudo, but my keyboard map was messed up (did not notice I was using Japanese keyboard layout the whole time which became default immediately after the window system is fired up. So i could log in initially every time but after that the none letter characters I typed where not the same as what the system received)
            – Reiner
            Jun 13 '15 at 15:37






            Thank you for this hint. It was not the reason but it lead to finding the reason: Nothing was wrong with sudo, but my keyboard map was messed up (did not notice I was using Japanese keyboard layout the whole time which became default immediately after the window system is fired up. So i could log in initially every time but after that the none letter characters I typed where not the same as what the system received)
            – Reiner
            Jun 13 '15 at 15:37














            What a beartrap! Glad it is solved.
            – Max Lemieux
            Jun 13 '15 at 17:59




            What a beartrap! Glad it is solved.
            – Max Lemieux
            Jun 13 '15 at 17:59













            1














            As per your comment, the reason for this was that your system was set to a different keyboard layout to the one you expected. I've run into that problem too. The keyboard shortcut to switch layout should work fine at the lock screen.



            I'm mainly writing this answer to correct a few misconceptions in your question.



            Max Lemieux's answer points out that the problem here was that you were typing the wrong password (not because you were making a mistake of course, but because you were typing on the wrong layout and had no way of knowing that because nothing shows up when the password is typed) and that is clear from the error you show:



            $ sudo more sudoers
            [sudo]password for wuzzle: (password entered)
            Sorry, try again.


            This error just means the wrong password was entered.



            You showed in your question your repeated efforts to fix this by adding yourself to the sudo group. You even accused Bash of lying to you when it said you were already in the sudo group(!) The commands you used to add yourself to the sudo group were correct, and you noticed that they returned no errors. If you had not been in the sudo group, this is what would have happened when you tried to use sudo:



            $ sudo uname -r
            [sudo] password for unicorn:
            unicorn is not in the sudoers file. This incident will be reported.


            You could have checked what groups you were in on the command line without needing sudo, using, for example, these commands:



            $ groups
            zanna adm cdrom sudo dip plugdev lpadmin sambashare
            $ id
            uid=1000(zanna) gid=1000(zanna) groups=1000(zanna),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),120(lpadmin),130(sambashare)


            You also said this




            Yet, after reboot and login I still can't sudo. For example:



            ls -l  /etc/sudoers


            shows it has this ownership



            -r--r------1 root root



            That's exactly what it should be, and if those ownerships and those permissions are changed, sudo will refuse to work very stubbornly until they have been fixed (of course you will need to somehow get a root shell to fix it because you won't be able to use sudo). You should never change the permissions of the sudoers file.




            Also, the date of the file /etc/sudoers indicates that it was unchanged even though I used before commands (as root) that I had expected should change the file.




            Adding a user to the sudo group does not change the sudoers file. If you examine the file, you will see how it is that adding a user to the sudo group gives them access to sudo:



            # Allow members of group sudo to execute any command
            %sudo ALL=(ALL:ALL) ALL


            So, no need for a line about each user - this one line plus group membership gives you all the privileges you'll need. As far as I know, the sudoers file is never edited automatically.



            If you ever do need to edit /etc/sudoers, be sure to use sudo visudo which won't let you save the file if you've introduced syntax errors.






            share|improve this answer




























              1














              As per your comment, the reason for this was that your system was set to a different keyboard layout to the one you expected. I've run into that problem too. The keyboard shortcut to switch layout should work fine at the lock screen.



              I'm mainly writing this answer to correct a few misconceptions in your question.



              Max Lemieux's answer points out that the problem here was that you were typing the wrong password (not because you were making a mistake of course, but because you were typing on the wrong layout and had no way of knowing that because nothing shows up when the password is typed) and that is clear from the error you show:



              $ sudo more sudoers
              [sudo]password for wuzzle: (password entered)
              Sorry, try again.


              This error just means the wrong password was entered.



              You showed in your question your repeated efforts to fix this by adding yourself to the sudo group. You even accused Bash of lying to you when it said you were already in the sudo group(!) The commands you used to add yourself to the sudo group were correct, and you noticed that they returned no errors. If you had not been in the sudo group, this is what would have happened when you tried to use sudo:



              $ sudo uname -r
              [sudo] password for unicorn:
              unicorn is not in the sudoers file. This incident will be reported.


              You could have checked what groups you were in on the command line without needing sudo, using, for example, these commands:



              $ groups
              zanna adm cdrom sudo dip plugdev lpadmin sambashare
              $ id
              uid=1000(zanna) gid=1000(zanna) groups=1000(zanna),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),120(lpadmin),130(sambashare)


              You also said this




              Yet, after reboot and login I still can't sudo. For example:



              ls -l  /etc/sudoers


              shows it has this ownership



              -r--r------1 root root



              That's exactly what it should be, and if those ownerships and those permissions are changed, sudo will refuse to work very stubbornly until they have been fixed (of course you will need to somehow get a root shell to fix it because you won't be able to use sudo). You should never change the permissions of the sudoers file.




              Also, the date of the file /etc/sudoers indicates that it was unchanged even though I used before commands (as root) that I had expected should change the file.




              Adding a user to the sudo group does not change the sudoers file. If you examine the file, you will see how it is that adding a user to the sudo group gives them access to sudo:



              # Allow members of group sudo to execute any command
              %sudo ALL=(ALL:ALL) ALL


              So, no need for a line about each user - this one line plus group membership gives you all the privileges you'll need. As far as I know, the sudoers file is never edited automatically.



              If you ever do need to edit /etc/sudoers, be sure to use sudo visudo which won't let you save the file if you've introduced syntax errors.






              share|improve this answer


























                1












                1








                1






                As per your comment, the reason for this was that your system was set to a different keyboard layout to the one you expected. I've run into that problem too. The keyboard shortcut to switch layout should work fine at the lock screen.



                I'm mainly writing this answer to correct a few misconceptions in your question.



                Max Lemieux's answer points out that the problem here was that you were typing the wrong password (not because you were making a mistake of course, but because you were typing on the wrong layout and had no way of knowing that because nothing shows up when the password is typed) and that is clear from the error you show:



                $ sudo more sudoers
                [sudo]password for wuzzle: (password entered)
                Sorry, try again.


                This error just means the wrong password was entered.



                You showed in your question your repeated efforts to fix this by adding yourself to the sudo group. You even accused Bash of lying to you when it said you were already in the sudo group(!) The commands you used to add yourself to the sudo group were correct, and you noticed that they returned no errors. If you had not been in the sudo group, this is what would have happened when you tried to use sudo:



                $ sudo uname -r
                [sudo] password for unicorn:
                unicorn is not in the sudoers file. This incident will be reported.


                You could have checked what groups you were in on the command line without needing sudo, using, for example, these commands:



                $ groups
                zanna adm cdrom sudo dip plugdev lpadmin sambashare
                $ id
                uid=1000(zanna) gid=1000(zanna) groups=1000(zanna),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),120(lpadmin),130(sambashare)


                You also said this




                Yet, after reboot and login I still can't sudo. For example:



                ls -l  /etc/sudoers


                shows it has this ownership



                -r--r------1 root root



                That's exactly what it should be, and if those ownerships and those permissions are changed, sudo will refuse to work very stubbornly until they have been fixed (of course you will need to somehow get a root shell to fix it because you won't be able to use sudo). You should never change the permissions of the sudoers file.




                Also, the date of the file /etc/sudoers indicates that it was unchanged even though I used before commands (as root) that I had expected should change the file.




                Adding a user to the sudo group does not change the sudoers file. If you examine the file, you will see how it is that adding a user to the sudo group gives them access to sudo:



                # Allow members of group sudo to execute any command
                %sudo ALL=(ALL:ALL) ALL


                So, no need for a line about each user - this one line plus group membership gives you all the privileges you'll need. As far as I know, the sudoers file is never edited automatically.



                If you ever do need to edit /etc/sudoers, be sure to use sudo visudo which won't let you save the file if you've introduced syntax errors.






                share|improve this answer














                As per your comment, the reason for this was that your system was set to a different keyboard layout to the one you expected. I've run into that problem too. The keyboard shortcut to switch layout should work fine at the lock screen.



                I'm mainly writing this answer to correct a few misconceptions in your question.



                Max Lemieux's answer points out that the problem here was that you were typing the wrong password (not because you were making a mistake of course, but because you were typing on the wrong layout and had no way of knowing that because nothing shows up when the password is typed) and that is clear from the error you show:



                $ sudo more sudoers
                [sudo]password for wuzzle: (password entered)
                Sorry, try again.


                This error just means the wrong password was entered.



                You showed in your question your repeated efforts to fix this by adding yourself to the sudo group. You even accused Bash of lying to you when it said you were already in the sudo group(!) The commands you used to add yourself to the sudo group were correct, and you noticed that they returned no errors. If you had not been in the sudo group, this is what would have happened when you tried to use sudo:



                $ sudo uname -r
                [sudo] password for unicorn:
                unicorn is not in the sudoers file. This incident will be reported.


                You could have checked what groups you were in on the command line without needing sudo, using, for example, these commands:



                $ groups
                zanna adm cdrom sudo dip plugdev lpadmin sambashare
                $ id
                uid=1000(zanna) gid=1000(zanna) groups=1000(zanna),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),120(lpadmin),130(sambashare)


                You also said this




                Yet, after reboot and login I still can't sudo. For example:



                ls -l  /etc/sudoers


                shows it has this ownership



                -r--r------1 root root



                That's exactly what it should be, and if those ownerships and those permissions are changed, sudo will refuse to work very stubbornly until they have been fixed (of course you will need to somehow get a root shell to fix it because you won't be able to use sudo). You should never change the permissions of the sudoers file.




                Also, the date of the file /etc/sudoers indicates that it was unchanged even though I used before commands (as root) that I had expected should change the file.




                Adding a user to the sudo group does not change the sudoers file. If you examine the file, you will see how it is that adding a user to the sudo group gives them access to sudo:



                # Allow members of group sudo to execute any command
                %sudo ALL=(ALL:ALL) ALL


                So, no need for a line about each user - this one line plus group membership gives you all the privileges you'll need. As far as I know, the sudoers file is never edited automatically.



                If you ever do need to edit /etc/sudoers, be sure to use sudo visudo which won't let you save the file if you've introduced syntax errors.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Dec 19 '18 at 20:40

























                answered Dec 19 '18 at 20:28









                ZannaZanna

                50.3k13133241




                50.3k13133241






























                    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%2f635836%2fadded-myself-to-sudo-group-in-recovery-mode-but-still-cannot-use-sudo-sorry%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

                    Quarter-circle Tiles

                    build a pushdown automaton that recognizes the reverse language of a given pushdown automaton?

                    Mont Emei