Kubuntu - can't get past login screen and whiptail error

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












I was working fine earlier today in kubuntu zesty 17.04. I tried to do a restart and then couldn't get past the login screen. It accepted the password but just brought the login screen up again.



I tried them to go into recovery mode and see if any errors appeared. The shell loaded but the filesystem was read only. First it appeared there was an error with mounting the encrypted swap partition. so I disabled mounting that temporarily but it didn't fix the issue. I loaded up a live CD and ran fsck too. No joy.



There is another error in the recovery shell,




/usr/bin/env: 'node': no such file or directory




Then, on the next line:




couldn't find whiptail, starting root shell instead of recovery menu




When I try sudo apt-get install whiptail it says it's already installed.










share|improve this question



















  • 1




    16.10 (Yakkety) is outside support. You may find askubuntu.com/questions/110477/… as well as askubuntu.com/questions/16366/… useful.
    – Elder Geek
    Feb 5 at 18:53










  • Oops it's zesty 17.04 - forgot what version it was.
    – ankles
    Feb 5 at 19:26










  • Currently supported releases are listed under current
    – Elder Geek
    Feb 6 at 13:47














up vote
0
down vote

favorite












I was working fine earlier today in kubuntu zesty 17.04. I tried to do a restart and then couldn't get past the login screen. It accepted the password but just brought the login screen up again.



I tried them to go into recovery mode and see if any errors appeared. The shell loaded but the filesystem was read only. First it appeared there was an error with mounting the encrypted swap partition. so I disabled mounting that temporarily but it didn't fix the issue. I loaded up a live CD and ran fsck too. No joy.



There is another error in the recovery shell,




/usr/bin/env: 'node': no such file or directory




Then, on the next line:




couldn't find whiptail, starting root shell instead of recovery menu




When I try sudo apt-get install whiptail it says it's already installed.










share|improve this question



















  • 1




    16.10 (Yakkety) is outside support. You may find askubuntu.com/questions/110477/… as well as askubuntu.com/questions/16366/… useful.
    – Elder Geek
    Feb 5 at 18:53










  • Oops it's zesty 17.04 - forgot what version it was.
    – ankles
    Feb 5 at 19:26










  • Currently supported releases are listed under current
    – Elder Geek
    Feb 6 at 13:47












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I was working fine earlier today in kubuntu zesty 17.04. I tried to do a restart and then couldn't get past the login screen. It accepted the password but just brought the login screen up again.



I tried them to go into recovery mode and see if any errors appeared. The shell loaded but the filesystem was read only. First it appeared there was an error with mounting the encrypted swap partition. so I disabled mounting that temporarily but it didn't fix the issue. I loaded up a live CD and ran fsck too. No joy.



There is another error in the recovery shell,




/usr/bin/env: 'node': no such file or directory




Then, on the next line:




couldn't find whiptail, starting root shell instead of recovery menu




When I try sudo apt-get install whiptail it says it's already installed.










share|improve this question















I was working fine earlier today in kubuntu zesty 17.04. I tried to do a restart and then couldn't get past the login screen. It accepted the password but just brought the login screen up again.



I tried them to go into recovery mode and see if any errors appeared. The shell loaded but the filesystem was read only. First it appeared there was an error with mounting the encrypted swap partition. so I disabled mounting that temporarily but it didn't fix the issue. I loaded up a live CD and ran fsck too. No joy.



There is another error in the recovery shell,




/usr/bin/env: 'node': no such file or directory




Then, on the next line:




couldn't find whiptail, starting root shell instead of recovery menu




When I try sudo apt-get install whiptail it says it's already installed.







boot kubuntu filesystem login-screen






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 5 at 19:26

























asked Feb 5 at 18:39









ankles

12




12







  • 1




    16.10 (Yakkety) is outside support. You may find askubuntu.com/questions/110477/… as well as askubuntu.com/questions/16366/… useful.
    – Elder Geek
    Feb 5 at 18:53










  • Oops it's zesty 17.04 - forgot what version it was.
    – ankles
    Feb 5 at 19:26










  • Currently supported releases are listed under current
    – Elder Geek
    Feb 6 at 13:47












  • 1




    16.10 (Yakkety) is outside support. You may find askubuntu.com/questions/110477/… as well as askubuntu.com/questions/16366/… useful.
    – Elder Geek
    Feb 5 at 18:53










  • Oops it's zesty 17.04 - forgot what version it was.
    – ankles
    Feb 5 at 19:26










  • Currently supported releases are listed under current
    – Elder Geek
    Feb 6 at 13:47







1




1




16.10 (Yakkety) is outside support. You may find askubuntu.com/questions/110477/… as well as askubuntu.com/questions/16366/… useful.
– Elder Geek
Feb 5 at 18:53




16.10 (Yakkety) is outside support. You may find askubuntu.com/questions/110477/… as well as askubuntu.com/questions/16366/… useful.
– Elder Geek
Feb 5 at 18:53












Oops it's zesty 17.04 - forgot what version it was.
– ankles
Feb 5 at 19:26




Oops it's zesty 17.04 - forgot what version it was.
– ankles
Feb 5 at 19:26












Currently supported releases are listed under current
– Elder Geek
Feb 6 at 13:47




Currently supported releases are listed under current
– Elder Geek
Feb 6 at 13:47










1 Answer
1






active

oldest

votes

















up vote
0
down vote



accepted










Managed to solve it:



1) I'd forgotten that I can enter command line from the login screen with CTRL + ALT + F2.



2) I didn't understand the support for zesty had expired, I did a dist upgrade and everything worked fine after that. I must have accidentally turned off notifications that zesty had run out as I didn't see a message about it...






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',
    convertImagesToLinks: true,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    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%2f1003336%2fkubuntu-cant-get-past-login-screen-and-whiptail-error%23new-answer', 'question_page');

    );

    Post as a guest






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote



    accepted










    Managed to solve it:



    1) I'd forgotten that I can enter command line from the login screen with CTRL + ALT + F2.



    2) I didn't understand the support for zesty had expired, I did a dist upgrade and everything worked fine after that. I must have accidentally turned off notifications that zesty had run out as I didn't see a message about it...






    share|improve this answer
























      up vote
      0
      down vote



      accepted










      Managed to solve it:



      1) I'd forgotten that I can enter command line from the login screen with CTRL + ALT + F2.



      2) I didn't understand the support for zesty had expired, I did a dist upgrade and everything worked fine after that. I must have accidentally turned off notifications that zesty had run out as I didn't see a message about it...






      share|improve this answer






















        up vote
        0
        down vote



        accepted







        up vote
        0
        down vote



        accepted






        Managed to solve it:



        1) I'd forgotten that I can enter command line from the login screen with CTRL + ALT + F2.



        2) I didn't understand the support for zesty had expired, I did a dist upgrade and everything worked fine after that. I must have accidentally turned off notifications that zesty had run out as I didn't see a message about it...






        share|improve this answer












        Managed to solve it:



        1) I'd forgotten that I can enter command line from the login screen with CTRL + ALT + F2.



        2) I didn't understand the support for zesty had expired, I did a dist upgrade and everything worked fine after that. I must have accidentally turned off notifications that zesty had run out as I didn't see a message about it...







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 6 at 9:28









        ankles

        12




        12



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1003336%2fkubuntu-cant-get-past-login-screen-and-whiptail-error%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            Running the scala interactive shell from the command line

            Unable to execute new pre-installation script (/var/lib/dpkg/tmp.ci/preinst)

            Do not install recommended packages of dependencies