Ubuntu 18.04 on login loop, even with correct password












3















I installed Ubuntu 18.04 yesterday, done some app installation and configurations and went to sleep. This morning, the login simply didn't work: the system is unable to log into my session, even with the correct password. Every time I try it, it flashes the screen into black and purple, the mouse pointer is available, but it flashes back to the login screen again: no error message prompts and I spent quite some time amusing myself trying to win it by attrition =). I also tried switch over to Wayland, and the same result: screen flashes to black, couple of seconds later, I'm back at the login stage.



There is nothing wrong with my password, since I can log into my user account on the Terminal (CTRL+ALT+F1). Once there, I did a sudo apt update/upgrade in the hopes it'd fix something, but my system was up to date and it didn't solve anything after I rebooted.



I've seen a lot of similar reports on the internet and the only solution that it seemed worthwhile to my noobish eyes was removing/deleting the .Xauthority file. But when I tried it, the return I got was that there was no such file on my Home directory. The other solutions applied to people upgrading their systems - mine was a fresh install - or with pretty specific hardware and conditions that don't apply to me.



So, what should I do to fix this?










share|improve this question


















  • 2





    Possible duplicate of Ubuntu gets stuck in a login loop

    – Elder Geek
    Jul 25 '18 at 21:43











  • Did you find a solution for this? I have the same problem and the solution mentioned on the above link does not work for Ubuntu 18.04

    – Sumit
    Sep 25 '18 at 6:37











  • Check again ls -l ~/.Xauthority ls -l ~/.ICEauthority ls -ld ~

    – Vijay
    Oct 30 '18 at 15:35


















3















I installed Ubuntu 18.04 yesterday, done some app installation and configurations and went to sleep. This morning, the login simply didn't work: the system is unable to log into my session, even with the correct password. Every time I try it, it flashes the screen into black and purple, the mouse pointer is available, but it flashes back to the login screen again: no error message prompts and I spent quite some time amusing myself trying to win it by attrition =). I also tried switch over to Wayland, and the same result: screen flashes to black, couple of seconds later, I'm back at the login stage.



There is nothing wrong with my password, since I can log into my user account on the Terminal (CTRL+ALT+F1). Once there, I did a sudo apt update/upgrade in the hopes it'd fix something, but my system was up to date and it didn't solve anything after I rebooted.



I've seen a lot of similar reports on the internet and the only solution that it seemed worthwhile to my noobish eyes was removing/deleting the .Xauthority file. But when I tried it, the return I got was that there was no such file on my Home directory. The other solutions applied to people upgrading their systems - mine was a fresh install - or with pretty specific hardware and conditions that don't apply to me.



So, what should I do to fix this?










share|improve this question


















  • 2





    Possible duplicate of Ubuntu gets stuck in a login loop

    – Elder Geek
    Jul 25 '18 at 21:43











  • Did you find a solution for this? I have the same problem and the solution mentioned on the above link does not work for Ubuntu 18.04

    – Sumit
    Sep 25 '18 at 6:37











  • Check again ls -l ~/.Xauthority ls -l ~/.ICEauthority ls -ld ~

    – Vijay
    Oct 30 '18 at 15:35
















3












3








3








I installed Ubuntu 18.04 yesterday, done some app installation and configurations and went to sleep. This morning, the login simply didn't work: the system is unable to log into my session, even with the correct password. Every time I try it, it flashes the screen into black and purple, the mouse pointer is available, but it flashes back to the login screen again: no error message prompts and I spent quite some time amusing myself trying to win it by attrition =). I also tried switch over to Wayland, and the same result: screen flashes to black, couple of seconds later, I'm back at the login stage.



There is nothing wrong with my password, since I can log into my user account on the Terminal (CTRL+ALT+F1). Once there, I did a sudo apt update/upgrade in the hopes it'd fix something, but my system was up to date and it didn't solve anything after I rebooted.



I've seen a lot of similar reports on the internet and the only solution that it seemed worthwhile to my noobish eyes was removing/deleting the .Xauthority file. But when I tried it, the return I got was that there was no such file on my Home directory. The other solutions applied to people upgrading their systems - mine was a fresh install - or with pretty specific hardware and conditions that don't apply to me.



So, what should I do to fix this?










share|improve this question














I installed Ubuntu 18.04 yesterday, done some app installation and configurations and went to sleep. This morning, the login simply didn't work: the system is unable to log into my session, even with the correct password. Every time I try it, it flashes the screen into black and purple, the mouse pointer is available, but it flashes back to the login screen again: no error message prompts and I spent quite some time amusing myself trying to win it by attrition =). I also tried switch over to Wayland, and the same result: screen flashes to black, couple of seconds later, I'm back at the login stage.



There is nothing wrong with my password, since I can log into my user account on the Terminal (CTRL+ALT+F1). Once there, I did a sudo apt update/upgrade in the hopes it'd fix something, but my system was up to date and it didn't solve anything after I rebooted.



I've seen a lot of similar reports on the internet and the only solution that it seemed worthwhile to my noobish eyes was removing/deleting the .Xauthority file. But when I tried it, the return I got was that there was no such file on my Home directory. The other solutions applied to people upgrading their systems - mine was a fresh install - or with pretty specific hardware and conditions that don't apply to me.



So, what should I do to fix this?







18.04






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jul 25 '18 at 18:31









wowbaggerwowbagger

2614




2614








  • 2





    Possible duplicate of Ubuntu gets stuck in a login loop

    – Elder Geek
    Jul 25 '18 at 21:43











  • Did you find a solution for this? I have the same problem and the solution mentioned on the above link does not work for Ubuntu 18.04

    – Sumit
    Sep 25 '18 at 6:37











  • Check again ls -l ~/.Xauthority ls -l ~/.ICEauthority ls -ld ~

    – Vijay
    Oct 30 '18 at 15:35
















  • 2





    Possible duplicate of Ubuntu gets stuck in a login loop

    – Elder Geek
    Jul 25 '18 at 21:43











  • Did you find a solution for this? I have the same problem and the solution mentioned on the above link does not work for Ubuntu 18.04

    – Sumit
    Sep 25 '18 at 6:37











  • Check again ls -l ~/.Xauthority ls -l ~/.ICEauthority ls -ld ~

    – Vijay
    Oct 30 '18 at 15:35










2




2





Possible duplicate of Ubuntu gets stuck in a login loop

– Elder Geek
Jul 25 '18 at 21:43





Possible duplicate of Ubuntu gets stuck in a login loop

– Elder Geek
Jul 25 '18 at 21:43













Did you find a solution for this? I have the same problem and the solution mentioned on the above link does not work for Ubuntu 18.04

– Sumit
Sep 25 '18 at 6:37





Did you find a solution for this? I have the same problem and the solution mentioned on the above link does not work for Ubuntu 18.04

– Sumit
Sep 25 '18 at 6:37













Check again ls -l ~/.Xauthority ls -l ~/.ICEauthority ls -ld ~

– Vijay
Oct 30 '18 at 15:35







Check again ls -l ~/.Xauthority ls -l ~/.ICEauthority ls -ld ~

– Vijay
Oct 30 '18 at 15:35












5 Answers
5






active

oldest

votes


















1














I had the same problem.

Then I found out that I accidentally changed the ownership of my /home/username directory to root.



So you can go to the terminal by CTRL+ALT+F1, and change the username directory ownership with



sudo chown username:username -R /home/username





share|improve this answer

































    1














    I ended up solving this by disabling secure boot on my notebook. As I understand, my issue was caused by wonky Nvidia drivers.






    share|improve this answer































      0














      Experienced the same problem today for the first time since moving on to Beaver. Weirdly immediately post full wizard install.

      Initially I thought it was a Wayland issue but despite attempts to force other compositors the issue remained until I cracked-open a Shell and removed my freshly created user /home folder. Upon the next initialisation of my chosen GDM I was shown the new user config wizard and all has been fine since.






      share|improve this answer































        0














        I just spent WAAAY too much time solving this issue. What finally solved the issue was replacing the /usr/local/lib/libreadline.so.7 library with a link to /lib/x86_64-linux-gnu/libreadline.so.7



        sudo mv /usr/local/lib/libreadline.so.7 /usr/local/lib/back.libreadline.so.7
        sudo mv /usr/local/lib/libreadline.so /usr/local/lib/back.libreadline.so
        sudo ln -s /lib/x86_64-linux-gnu/libreadline.so.7 /usr/local/lib/libreadline.so.7
        sudo ln -s /usr/local/lib/libreadline.so.7 /usr/local/lib/libreadline.so


        A good indication that there was a problem was that gawk did not work because of the same missing external in libreadline with:



        $ gawk
        gawk: symbol lookup error: /usr/local/lib/libreadline.so.7: undefined symbol: UP


        My ~/.Xauthority was fine, no amounts of updates made any difference.
        Right after my upgrade from to Ubuntu 18.04.1, my system would stop booting in the middle somewhere. I switched to lightdm from gdm3 with



        sudo dpkg-reconfigure lightdm


        and the system would boot but then I could not login.



        I hope this can help somebody.






        share|improve this answer































          0














          In my case, the issue was linked to my home directory beeing encrypted with ecryptfs, it seems.



          I logged in to the console (Ctrl+Alt+F1), and installed ecryptfs-utils :



          sudo apt-get install ecryptfs-utils


          It solved the problem.






          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%2f1059458%2fubuntu-18-04-on-login-loop-even-with-correct-password%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            5 Answers
            5






            active

            oldest

            votes








            5 Answers
            5






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            I had the same problem.

            Then I found out that I accidentally changed the ownership of my /home/username directory to root.



            So you can go to the terminal by CTRL+ALT+F1, and change the username directory ownership with



            sudo chown username:username -R /home/username





            share|improve this answer






























              1














              I had the same problem.

              Then I found out that I accidentally changed the ownership of my /home/username directory to root.



              So you can go to the terminal by CTRL+ALT+F1, and change the username directory ownership with



              sudo chown username:username -R /home/username





              share|improve this answer




























                1












                1








                1







                I had the same problem.

                Then I found out that I accidentally changed the ownership of my /home/username directory to root.



                So you can go to the terminal by CTRL+ALT+F1, and change the username directory ownership with



                sudo chown username:username -R /home/username





                share|improve this answer















                I had the same problem.

                Then I found out that I accidentally changed the ownership of my /home/username directory to root.



                So you can go to the terminal by CTRL+ALT+F1, and change the username directory ownership with



                sudo chown username:username -R /home/username






                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Sep 27 '18 at 23:40









                zx485

                1,45231114




                1,45231114










                answered Sep 27 '18 at 18:43









                HosseinNedaeeHosseinNedaee

                111




                111

























                    1














                    I ended up solving this by disabling secure boot on my notebook. As I understand, my issue was caused by wonky Nvidia drivers.






                    share|improve this answer




























                      1














                      I ended up solving this by disabling secure boot on my notebook. As I understand, my issue was caused by wonky Nvidia drivers.






                      share|improve this answer


























                        1












                        1








                        1







                        I ended up solving this by disabling secure boot on my notebook. As I understand, my issue was caused by wonky Nvidia drivers.






                        share|improve this answer













                        I ended up solving this by disabling secure boot on my notebook. As I understand, my issue was caused by wonky Nvidia drivers.







                        share|improve this answer












                        share|improve this answer



                        share|improve this answer










                        answered Nov 19 '18 at 21:49









                        wowbaggerwowbagger

                        2614




                        2614























                            0














                            Experienced the same problem today for the first time since moving on to Beaver. Weirdly immediately post full wizard install.

                            Initially I thought it was a Wayland issue but despite attempts to force other compositors the issue remained until I cracked-open a Shell and removed my freshly created user /home folder. Upon the next initialisation of my chosen GDM I was shown the new user config wizard and all has been fine since.






                            share|improve this answer




























                              0














                              Experienced the same problem today for the first time since moving on to Beaver. Weirdly immediately post full wizard install.

                              Initially I thought it was a Wayland issue but despite attempts to force other compositors the issue remained until I cracked-open a Shell and removed my freshly created user /home folder. Upon the next initialisation of my chosen GDM I was shown the new user config wizard and all has been fine since.






                              share|improve this answer


























                                0












                                0








                                0







                                Experienced the same problem today for the first time since moving on to Beaver. Weirdly immediately post full wizard install.

                                Initially I thought it was a Wayland issue but despite attempts to force other compositors the issue remained until I cracked-open a Shell and removed my freshly created user /home folder. Upon the next initialisation of my chosen GDM I was shown the new user config wizard and all has been fine since.






                                share|improve this answer













                                Experienced the same problem today for the first time since moving on to Beaver. Weirdly immediately post full wizard install.

                                Initially I thought it was a Wayland issue but despite attempts to force other compositors the issue remained until I cracked-open a Shell and removed my freshly created user /home folder. Upon the next initialisation of my chosen GDM I was shown the new user config wizard and all has been fine since.







                                share|improve this answer












                                share|improve this answer



                                share|improve this answer










                                answered Nov 18 '18 at 19:05









                                RobRob

                                1




                                1























                                    0














                                    I just spent WAAAY too much time solving this issue. What finally solved the issue was replacing the /usr/local/lib/libreadline.so.7 library with a link to /lib/x86_64-linux-gnu/libreadline.so.7



                                    sudo mv /usr/local/lib/libreadline.so.7 /usr/local/lib/back.libreadline.so.7
                                    sudo mv /usr/local/lib/libreadline.so /usr/local/lib/back.libreadline.so
                                    sudo ln -s /lib/x86_64-linux-gnu/libreadline.so.7 /usr/local/lib/libreadline.so.7
                                    sudo ln -s /usr/local/lib/libreadline.so.7 /usr/local/lib/libreadline.so


                                    A good indication that there was a problem was that gawk did not work because of the same missing external in libreadline with:



                                    $ gawk
                                    gawk: symbol lookup error: /usr/local/lib/libreadline.so.7: undefined symbol: UP


                                    My ~/.Xauthority was fine, no amounts of updates made any difference.
                                    Right after my upgrade from to Ubuntu 18.04.1, my system would stop booting in the middle somewhere. I switched to lightdm from gdm3 with



                                    sudo dpkg-reconfigure lightdm


                                    and the system would boot but then I could not login.



                                    I hope this can help somebody.






                                    share|improve this answer




























                                      0














                                      I just spent WAAAY too much time solving this issue. What finally solved the issue was replacing the /usr/local/lib/libreadline.so.7 library with a link to /lib/x86_64-linux-gnu/libreadline.so.7



                                      sudo mv /usr/local/lib/libreadline.so.7 /usr/local/lib/back.libreadline.so.7
                                      sudo mv /usr/local/lib/libreadline.so /usr/local/lib/back.libreadline.so
                                      sudo ln -s /lib/x86_64-linux-gnu/libreadline.so.7 /usr/local/lib/libreadline.so.7
                                      sudo ln -s /usr/local/lib/libreadline.so.7 /usr/local/lib/libreadline.so


                                      A good indication that there was a problem was that gawk did not work because of the same missing external in libreadline with:



                                      $ gawk
                                      gawk: symbol lookup error: /usr/local/lib/libreadline.so.7: undefined symbol: UP


                                      My ~/.Xauthority was fine, no amounts of updates made any difference.
                                      Right after my upgrade from to Ubuntu 18.04.1, my system would stop booting in the middle somewhere. I switched to lightdm from gdm3 with



                                      sudo dpkg-reconfigure lightdm


                                      and the system would boot but then I could not login.



                                      I hope this can help somebody.






                                      share|improve this answer


























                                        0












                                        0








                                        0







                                        I just spent WAAAY too much time solving this issue. What finally solved the issue was replacing the /usr/local/lib/libreadline.so.7 library with a link to /lib/x86_64-linux-gnu/libreadline.so.7



                                        sudo mv /usr/local/lib/libreadline.so.7 /usr/local/lib/back.libreadline.so.7
                                        sudo mv /usr/local/lib/libreadline.so /usr/local/lib/back.libreadline.so
                                        sudo ln -s /lib/x86_64-linux-gnu/libreadline.so.7 /usr/local/lib/libreadline.so.7
                                        sudo ln -s /usr/local/lib/libreadline.so.7 /usr/local/lib/libreadline.so


                                        A good indication that there was a problem was that gawk did not work because of the same missing external in libreadline with:



                                        $ gawk
                                        gawk: symbol lookup error: /usr/local/lib/libreadline.so.7: undefined symbol: UP


                                        My ~/.Xauthority was fine, no amounts of updates made any difference.
                                        Right after my upgrade from to Ubuntu 18.04.1, my system would stop booting in the middle somewhere. I switched to lightdm from gdm3 with



                                        sudo dpkg-reconfigure lightdm


                                        and the system would boot but then I could not login.



                                        I hope this can help somebody.






                                        share|improve this answer













                                        I just spent WAAAY too much time solving this issue. What finally solved the issue was replacing the /usr/local/lib/libreadline.so.7 library with a link to /lib/x86_64-linux-gnu/libreadline.so.7



                                        sudo mv /usr/local/lib/libreadline.so.7 /usr/local/lib/back.libreadline.so.7
                                        sudo mv /usr/local/lib/libreadline.so /usr/local/lib/back.libreadline.so
                                        sudo ln -s /lib/x86_64-linux-gnu/libreadline.so.7 /usr/local/lib/libreadline.so.7
                                        sudo ln -s /usr/local/lib/libreadline.so.7 /usr/local/lib/libreadline.so


                                        A good indication that there was a problem was that gawk did not work because of the same missing external in libreadline with:



                                        $ gawk
                                        gawk: symbol lookup error: /usr/local/lib/libreadline.so.7: undefined symbol: UP


                                        My ~/.Xauthority was fine, no amounts of updates made any difference.
                                        Right after my upgrade from to Ubuntu 18.04.1, my system would stop booting in the middle somewhere. I switched to lightdm from gdm3 with



                                        sudo dpkg-reconfigure lightdm


                                        and the system would boot but then I could not login.



                                        I hope this can help somebody.







                                        share|improve this answer












                                        share|improve this answer



                                        share|improve this answer










                                        answered Nov 25 '18 at 4:24









                                        user1683793user1683793

                                        1011




                                        1011























                                            0














                                            In my case, the issue was linked to my home directory beeing encrypted with ecryptfs, it seems.



                                            I logged in to the console (Ctrl+Alt+F1), and installed ecryptfs-utils :



                                            sudo apt-get install ecryptfs-utils


                                            It solved the problem.






                                            share|improve this answer




























                                              0














                                              In my case, the issue was linked to my home directory beeing encrypted with ecryptfs, it seems.



                                              I logged in to the console (Ctrl+Alt+F1), and installed ecryptfs-utils :



                                              sudo apt-get install ecryptfs-utils


                                              It solved the problem.






                                              share|improve this answer


























                                                0












                                                0








                                                0







                                                In my case, the issue was linked to my home directory beeing encrypted with ecryptfs, it seems.



                                                I logged in to the console (Ctrl+Alt+F1), and installed ecryptfs-utils :



                                                sudo apt-get install ecryptfs-utils


                                                It solved the problem.






                                                share|improve this answer













                                                In my case, the issue was linked to my home directory beeing encrypted with ecryptfs, it seems.



                                                I logged in to the console (Ctrl+Alt+F1), and installed ecryptfs-utils :



                                                sudo apt-get install ecryptfs-utils


                                                It solved the problem.







                                                share|improve this answer












                                                share|improve this answer



                                                share|improve this answer










                                                answered Dec 14 '18 at 12:40









                                                dplampdplamp

                                                314




                                                314






























                                                    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.




                                                    draft saved


                                                    draft discarded














                                                    StackExchange.ready(
                                                    function () {
                                                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1059458%2fubuntu-18-04-on-login-loop-even-with-correct-password%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

                                                    GameSpot

                                                    connect to host localhost port 22: Connection refused

                                                    Getting a Wifi WPA2 wifi connection