Updated from 16.04 to 18.04 and having issues booting

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








up vote
2
down vote

favorite
2












I just updated from 16.04 to 18.04. Upon restarting I ended up at what appears to be the terminal. I was prompted for my login and password and got links to documentation, management, and support, as well as a little message about meltdown and spectre. Below that is:



[80.133769] Could not find key with description: [alphanumericstring]
[80.133922] could not find valid key in user session keyring for sig specified in mount option[samestringasabove]
[80.134129] Error parsing options; rc = [-2]


What is happening here and how do I get to my desktop? I am unsure if that key string should remain private so I left it out.







share|improve this question


























    up vote
    2
    down vote

    favorite
    2












    I just updated from 16.04 to 18.04. Upon restarting I ended up at what appears to be the terminal. I was prompted for my login and password and got links to documentation, management, and support, as well as a little message about meltdown and spectre. Below that is:



    [80.133769] Could not find key with description: [alphanumericstring]
    [80.133922] could not find valid key in user session keyring for sig specified in mount option[samestringasabove]
    [80.134129] Error parsing options; rc = [-2]


    What is happening here and how do I get to my desktop? I am unsure if that key string should remain private so I left it out.







    share|improve this question
























      up vote
      2
      down vote

      favorite
      2









      up vote
      2
      down vote

      favorite
      2






      2





      I just updated from 16.04 to 18.04. Upon restarting I ended up at what appears to be the terminal. I was prompted for my login and password and got links to documentation, management, and support, as well as a little message about meltdown and spectre. Below that is:



      [80.133769] Could not find key with description: [alphanumericstring]
      [80.133922] could not find valid key in user session keyring for sig specified in mount option[samestringasabove]
      [80.134129] Error parsing options; rc = [-2]


      What is happening here and how do I get to my desktop? I am unsure if that key string should remain private so I left it out.







      share|improve this question














      I just updated from 16.04 to 18.04. Upon restarting I ended up at what appears to be the terminal. I was prompted for my login and password and got links to documentation, management, and support, as well as a little message about meltdown and spectre. Below that is:



      [80.133769] Could not find key with description: [alphanumericstring]
      [80.133922] could not find valid key in user session keyring for sig specified in mount option[samestringasabove]
      [80.134129] Error parsing options; rc = [-2]


      What is happening here and how do I get to my desktop? I am unsure if that key string should remain private so I left it out.









      share|improve this question













      share|improve this question




      share|improve this question








      edited May 10 at 21:39









      Terrance

      17.2k23783




      17.2k23783










      asked May 10 at 21:37









      Jeffoh

      112




      112




















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          0
          down vote













          You are hitting this bug:
          https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658



          I have the same problem and I haven't found a way to fix it.



          There are a few workarounds mentioned in the report but none of them worked for me.



          Keep reading for what did work to get my system working again:



          There is a chance that this is not really your problem. In my local instance this seemed to be an issue with the graphics drivers, as (after installing SDDM from the command line) I was seeing the mouse cursor, but I didn't see the log-in screen. I ended up in this question because the message you posted was the only error message I saw. However, if you look into /var/log/X11.0.log you will see that it fails to load libGL.so.1, and it tries to use Vesa. While digging into the issue I discovered that libglx-mesa0 libgl1-mesa-dri and some other packages were corrupted and had missing configurations and files



          What I did to fix this:
          I purged all xorg, xserver*, lightdm, gdm3, sddm, libglx*, libgl0, libgl1 and everything I could find related to the UI. Specifically around libGL.so.1 (apt-file find libGL.so.1) and then installed it again using apt.



          Of course I ended up removing most of my system and restarted to install all packages from the ground, but at some point in this mess, I reinstalled libgl1-mesa-dri (+dependencies), sddm and kde-plasma-desktop, and I was finally able to boot into my system again. I understand this answer is quite chaotic, but this is what worked for me, and the real reason behind my issues was not related to the error message you are seeing, but to a broken mesa installation. This may be your case too.



          As a side note I would like to warn you that at some point I stopped seeing errors about libGL.so.1 in my X logs, but it kept refusing to load the drivers anyway, (and SDDM didn't show the log-in screen either!). So I kept removing and reinstalling packages around mesa and libgl* until my installation started working again.



          Good luck!






          share|improve this answer



























            up vote
            0
            down vote













            I had the same problem after upgrading to 18.04. The computer would boot into text terminal, and I could start the X Session with startx. I could resolve the problem with:
            sudo apt-get install --reinstall gdm3



            It seems this is a problem with the display manager and not necessarily linked to the ecryptfs bug. I think I was using lightdm before the update which is not the default.






            share|improve this answer








            New contributor




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

















              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%2f1034676%2fupdated-from-16-04-to-18-04-and-having-issues-booting%23new-answer', 'question_page');

              );

              Post as a guest






























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes








              up vote
              0
              down vote













              You are hitting this bug:
              https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658



              I have the same problem and I haven't found a way to fix it.



              There are a few workarounds mentioned in the report but none of them worked for me.



              Keep reading for what did work to get my system working again:



              There is a chance that this is not really your problem. In my local instance this seemed to be an issue with the graphics drivers, as (after installing SDDM from the command line) I was seeing the mouse cursor, but I didn't see the log-in screen. I ended up in this question because the message you posted was the only error message I saw. However, if you look into /var/log/X11.0.log you will see that it fails to load libGL.so.1, and it tries to use Vesa. While digging into the issue I discovered that libglx-mesa0 libgl1-mesa-dri and some other packages were corrupted and had missing configurations and files



              What I did to fix this:
              I purged all xorg, xserver*, lightdm, gdm3, sddm, libglx*, libgl0, libgl1 and everything I could find related to the UI. Specifically around libGL.so.1 (apt-file find libGL.so.1) and then installed it again using apt.



              Of course I ended up removing most of my system and restarted to install all packages from the ground, but at some point in this mess, I reinstalled libgl1-mesa-dri (+dependencies), sddm and kde-plasma-desktop, and I was finally able to boot into my system again. I understand this answer is quite chaotic, but this is what worked for me, and the real reason behind my issues was not related to the error message you are seeing, but to a broken mesa installation. This may be your case too.



              As a side note I would like to warn you that at some point I stopped seeing errors about libGL.so.1 in my X logs, but it kept refusing to load the drivers anyway, (and SDDM didn't show the log-in screen either!). So I kept removing and reinstalling packages around mesa and libgl* until my installation started working again.



              Good luck!






              share|improve this answer
























                up vote
                0
                down vote













                You are hitting this bug:
                https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658



                I have the same problem and I haven't found a way to fix it.



                There are a few workarounds mentioned in the report but none of them worked for me.



                Keep reading for what did work to get my system working again:



                There is a chance that this is not really your problem. In my local instance this seemed to be an issue with the graphics drivers, as (after installing SDDM from the command line) I was seeing the mouse cursor, but I didn't see the log-in screen. I ended up in this question because the message you posted was the only error message I saw. However, if you look into /var/log/X11.0.log you will see that it fails to load libGL.so.1, and it tries to use Vesa. While digging into the issue I discovered that libglx-mesa0 libgl1-mesa-dri and some other packages were corrupted and had missing configurations and files



                What I did to fix this:
                I purged all xorg, xserver*, lightdm, gdm3, sddm, libglx*, libgl0, libgl1 and everything I could find related to the UI. Specifically around libGL.so.1 (apt-file find libGL.so.1) and then installed it again using apt.



                Of course I ended up removing most of my system and restarted to install all packages from the ground, but at some point in this mess, I reinstalled libgl1-mesa-dri (+dependencies), sddm and kde-plasma-desktop, and I was finally able to boot into my system again. I understand this answer is quite chaotic, but this is what worked for me, and the real reason behind my issues was not related to the error message you are seeing, but to a broken mesa installation. This may be your case too.



                As a side note I would like to warn you that at some point I stopped seeing errors about libGL.so.1 in my X logs, but it kept refusing to load the drivers anyway, (and SDDM didn't show the log-in screen either!). So I kept removing and reinstalling packages around mesa and libgl* until my installation started working again.



                Good luck!






                share|improve this answer






















                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  You are hitting this bug:
                  https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658



                  I have the same problem and I haven't found a way to fix it.



                  There are a few workarounds mentioned in the report but none of them worked for me.



                  Keep reading for what did work to get my system working again:



                  There is a chance that this is not really your problem. In my local instance this seemed to be an issue with the graphics drivers, as (after installing SDDM from the command line) I was seeing the mouse cursor, but I didn't see the log-in screen. I ended up in this question because the message you posted was the only error message I saw. However, if you look into /var/log/X11.0.log you will see that it fails to load libGL.so.1, and it tries to use Vesa. While digging into the issue I discovered that libglx-mesa0 libgl1-mesa-dri and some other packages were corrupted and had missing configurations and files



                  What I did to fix this:
                  I purged all xorg, xserver*, lightdm, gdm3, sddm, libglx*, libgl0, libgl1 and everything I could find related to the UI. Specifically around libGL.so.1 (apt-file find libGL.so.1) and then installed it again using apt.



                  Of course I ended up removing most of my system and restarted to install all packages from the ground, but at some point in this mess, I reinstalled libgl1-mesa-dri (+dependencies), sddm and kde-plasma-desktop, and I was finally able to boot into my system again. I understand this answer is quite chaotic, but this is what worked for me, and the real reason behind my issues was not related to the error message you are seeing, but to a broken mesa installation. This may be your case too.



                  As a side note I would like to warn you that at some point I stopped seeing errors about libGL.so.1 in my X logs, but it kept refusing to load the drivers anyway, (and SDDM didn't show the log-in screen either!). So I kept removing and reinstalling packages around mesa and libgl* until my installation started working again.



                  Good luck!






                  share|improve this answer












                  You are hitting this bug:
                  https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658



                  I have the same problem and I haven't found a way to fix it.



                  There are a few workarounds mentioned in the report but none of them worked for me.



                  Keep reading for what did work to get my system working again:



                  There is a chance that this is not really your problem. In my local instance this seemed to be an issue with the graphics drivers, as (after installing SDDM from the command line) I was seeing the mouse cursor, but I didn't see the log-in screen. I ended up in this question because the message you posted was the only error message I saw. However, if you look into /var/log/X11.0.log you will see that it fails to load libGL.so.1, and it tries to use Vesa. While digging into the issue I discovered that libglx-mesa0 libgl1-mesa-dri and some other packages were corrupted and had missing configurations and files



                  What I did to fix this:
                  I purged all xorg, xserver*, lightdm, gdm3, sddm, libglx*, libgl0, libgl1 and everything I could find related to the UI. Specifically around libGL.so.1 (apt-file find libGL.so.1) and then installed it again using apt.



                  Of course I ended up removing most of my system and restarted to install all packages from the ground, but at some point in this mess, I reinstalled libgl1-mesa-dri (+dependencies), sddm and kde-plasma-desktop, and I was finally able to boot into my system again. I understand this answer is quite chaotic, but this is what worked for me, and the real reason behind my issues was not related to the error message you are seeing, but to a broken mesa installation. This may be your case too.



                  As a side note I would like to warn you that at some point I stopped seeing errors about libGL.so.1 in my X logs, but it kept refusing to load the drivers anyway, (and SDDM didn't show the log-in screen either!). So I kept removing and reinstalling packages around mesa and libgl* until my installation started working again.



                  Good luck!







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jun 17 at 20:29









                  Emilio M.

                  416




                  416






















                      up vote
                      0
                      down vote













                      I had the same problem after upgrading to 18.04. The computer would boot into text terminal, and I could start the X Session with startx. I could resolve the problem with:
                      sudo apt-get install --reinstall gdm3



                      It seems this is a problem with the display manager and not necessarily linked to the ecryptfs bug. I think I was using lightdm before the update which is not the default.






                      share|improve this answer








                      New contributor




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





















                        up vote
                        0
                        down vote













                        I had the same problem after upgrading to 18.04. The computer would boot into text terminal, and I could start the X Session with startx. I could resolve the problem with:
                        sudo apt-get install --reinstall gdm3



                        It seems this is a problem with the display manager and not necessarily linked to the ecryptfs bug. I think I was using lightdm before the update which is not the default.






                        share|improve this answer








                        New contributor




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



















                          up vote
                          0
                          down vote










                          up vote
                          0
                          down vote









                          I had the same problem after upgrading to 18.04. The computer would boot into text terminal, and I could start the X Session with startx. I could resolve the problem with:
                          sudo apt-get install --reinstall gdm3



                          It seems this is a problem with the display manager and not necessarily linked to the ecryptfs bug. I think I was using lightdm before the update which is not the default.






                          share|improve this answer








                          New contributor




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









                          I had the same problem after upgrading to 18.04. The computer would boot into text terminal, and I could start the X Session with startx. I could resolve the problem with:
                          sudo apt-get install --reinstall gdm3



                          It seems this is a problem with the display manager and not necessarily linked to the ecryptfs bug. I think I was using lightdm before the update which is not the default.







                          share|improve this answer








                          New contributor




                          Pierre 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




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









                          answered Aug 25 at 14:59









                          Pierre

                          1




                          1




                          New contributor




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





                          New contributor





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






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






















                               

                              draft saved


                              draft discarded


























                               


                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1034676%2fupdated-from-16-04-to-18-04-and-having-issues-booting%23new-answer', 'question_page');

                              );

                              Post as a guest













































































                              Popular posts from this blog

                              pylint3 and pip3 broken

                              Missing snmpget and snmpwalk

                              How to enroll fingerprints to Ubuntu 17.10 with VFS491