Ubuntu freezes during boot





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















I'm running ubuntu 14.04 on a Acer E17 laptop. From one to another the computer seems to freeze during the boot sequence. It boots to grub without an issue, but when I select Ubuntu it seems to freeze on a black screen. No indication as to what it's doing or any error code. Normally it would display the word Ubuntu with 5 dots beneath it that change from white to red.



If I boot the recovery boot (of the same kernel) and in recovery immediately hit resume it boots normally and I can login.



I already tried to downgrade some recent updates using synaptic, but that did not help. The next thing I tried is to try to create some boot logs with bootlogd, but /var/log/boot.log remains empty. Does anyone have an idea where to go next?



Edit: after a couple of days /var/log/boot.log and /var/log/boot have some information, but no errors of any kind.



cat /var/log/boot produces this output: http://pastebin.com/FEjBveEG



cat /var/log/boot.log produces this output: http://pastebin.com/iycLg0p0
(formatting is off, no idea why, it isn't in the output)










share|improve this question
















bumped to the homepage by Community 21 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






















    1















    I'm running ubuntu 14.04 on a Acer E17 laptop. From one to another the computer seems to freeze during the boot sequence. It boots to grub without an issue, but when I select Ubuntu it seems to freeze on a black screen. No indication as to what it's doing or any error code. Normally it would display the word Ubuntu with 5 dots beneath it that change from white to red.



    If I boot the recovery boot (of the same kernel) and in recovery immediately hit resume it boots normally and I can login.



    I already tried to downgrade some recent updates using synaptic, but that did not help. The next thing I tried is to try to create some boot logs with bootlogd, but /var/log/boot.log remains empty. Does anyone have an idea where to go next?



    Edit: after a couple of days /var/log/boot.log and /var/log/boot have some information, but no errors of any kind.



    cat /var/log/boot produces this output: http://pastebin.com/FEjBveEG



    cat /var/log/boot.log produces this output: http://pastebin.com/iycLg0p0
    (formatting is off, no idea why, it isn't in the output)










    share|improve this question
















    bumped to the homepage by Community 21 hours ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      1












      1








      1


      2






      I'm running ubuntu 14.04 on a Acer E17 laptop. From one to another the computer seems to freeze during the boot sequence. It boots to grub without an issue, but when I select Ubuntu it seems to freeze on a black screen. No indication as to what it's doing or any error code. Normally it would display the word Ubuntu with 5 dots beneath it that change from white to red.



      If I boot the recovery boot (of the same kernel) and in recovery immediately hit resume it boots normally and I can login.



      I already tried to downgrade some recent updates using synaptic, but that did not help. The next thing I tried is to try to create some boot logs with bootlogd, but /var/log/boot.log remains empty. Does anyone have an idea where to go next?



      Edit: after a couple of days /var/log/boot.log and /var/log/boot have some information, but no errors of any kind.



      cat /var/log/boot produces this output: http://pastebin.com/FEjBveEG



      cat /var/log/boot.log produces this output: http://pastebin.com/iycLg0p0
      (formatting is off, no idea why, it isn't in the output)










      share|improve this question
















      I'm running ubuntu 14.04 on a Acer E17 laptop. From one to another the computer seems to freeze during the boot sequence. It boots to grub without an issue, but when I select Ubuntu it seems to freeze on a black screen. No indication as to what it's doing or any error code. Normally it would display the word Ubuntu with 5 dots beneath it that change from white to red.



      If I boot the recovery boot (of the same kernel) and in recovery immediately hit resume it boots normally and I can login.



      I already tried to downgrade some recent updates using synaptic, but that did not help. The next thing I tried is to try to create some boot logs with bootlogd, but /var/log/boot.log remains empty. Does anyone have an idea where to go next?



      Edit: after a couple of days /var/log/boot.log and /var/log/boot have some information, but no errors of any kind.



      cat /var/log/boot produces this output: http://pastebin.com/FEjBveEG



      cat /var/log/boot.log produces this output: http://pastebin.com/iycLg0p0
      (formatting is off, no idea why, it isn't in the output)







      14.04 boot






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jun 15 '16 at 15:47









      amc

      4,80462746




      4,80462746










      asked May 3 '15 at 6:28









      MartijnMartijn

      6115




      6115





      bumped to the homepage by Community 21 hours ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 21 hours ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Ubuntu actually waits for all the essential drivers and environment application to load before log you in. In my case, I intended to overwrite the default (lightdm unity) with gnome-shell, bit it failed and the boot sequence was waiting infinitely for it to run. So I need to rollback my changes but there isn't much i can do since I cant actually get myself to terminal (the "shift" + boot didn't work).



          Here's what I did to resolve the issue:




          1. Plugged in my usb bootable ubuntu and ran trial version.

          2. Browsed through the bootdrive and edited /etc/X11/default-display-manager.

          3. It didn't allow me to write so I assigned writable permission to it
            with sudo chmod 777 /etc/X11/ -R.

          4. Then I changed the line /usr/sbin/gdm to /usr/sbin/lightdm and the rebooted. By doing this I rolled back the changed from gnome-shell to lightdm, and I saved myself from reinstalling the system.






          share|improve this answer


























          • you don't need to change the permissions in step 3 -- simply use sudo with your editor to edit the file. this will avoid any future problems caused by incorrect permissions.

            – amc
            Jun 15 '16 at 15:45











          • yea ,i would have but i dont know why,the changes i made with sudo nano never been updated..so i just went to more obvious way of doing it.

            – Ry Van
            Jun 15 '16 at 17:05












          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%2f617572%2fubuntu-freezes-during-boot%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          Ubuntu actually waits for all the essential drivers and environment application to load before log you in. In my case, I intended to overwrite the default (lightdm unity) with gnome-shell, bit it failed and the boot sequence was waiting infinitely for it to run. So I need to rollback my changes but there isn't much i can do since I cant actually get myself to terminal (the "shift" + boot didn't work).



          Here's what I did to resolve the issue:




          1. Plugged in my usb bootable ubuntu and ran trial version.

          2. Browsed through the bootdrive and edited /etc/X11/default-display-manager.

          3. It didn't allow me to write so I assigned writable permission to it
            with sudo chmod 777 /etc/X11/ -R.

          4. Then I changed the line /usr/sbin/gdm to /usr/sbin/lightdm and the rebooted. By doing this I rolled back the changed from gnome-shell to lightdm, and I saved myself from reinstalling the system.






          share|improve this answer


























          • you don't need to change the permissions in step 3 -- simply use sudo with your editor to edit the file. this will avoid any future problems caused by incorrect permissions.

            – amc
            Jun 15 '16 at 15:45











          • yea ,i would have but i dont know why,the changes i made with sudo nano never been updated..so i just went to more obvious way of doing it.

            – Ry Van
            Jun 15 '16 at 17:05
















          0














          Ubuntu actually waits for all the essential drivers and environment application to load before log you in. In my case, I intended to overwrite the default (lightdm unity) with gnome-shell, bit it failed and the boot sequence was waiting infinitely for it to run. So I need to rollback my changes but there isn't much i can do since I cant actually get myself to terminal (the "shift" + boot didn't work).



          Here's what I did to resolve the issue:




          1. Plugged in my usb bootable ubuntu and ran trial version.

          2. Browsed through the bootdrive and edited /etc/X11/default-display-manager.

          3. It didn't allow me to write so I assigned writable permission to it
            with sudo chmod 777 /etc/X11/ -R.

          4. Then I changed the line /usr/sbin/gdm to /usr/sbin/lightdm and the rebooted. By doing this I rolled back the changed from gnome-shell to lightdm, and I saved myself from reinstalling the system.






          share|improve this answer


























          • you don't need to change the permissions in step 3 -- simply use sudo with your editor to edit the file. this will avoid any future problems caused by incorrect permissions.

            – amc
            Jun 15 '16 at 15:45











          • yea ,i would have but i dont know why,the changes i made with sudo nano never been updated..so i just went to more obvious way of doing it.

            – Ry Van
            Jun 15 '16 at 17:05














          0












          0








          0







          Ubuntu actually waits for all the essential drivers and environment application to load before log you in. In my case, I intended to overwrite the default (lightdm unity) with gnome-shell, bit it failed and the boot sequence was waiting infinitely for it to run. So I need to rollback my changes but there isn't much i can do since I cant actually get myself to terminal (the "shift" + boot didn't work).



          Here's what I did to resolve the issue:




          1. Plugged in my usb bootable ubuntu and ran trial version.

          2. Browsed through the bootdrive and edited /etc/X11/default-display-manager.

          3. It didn't allow me to write so I assigned writable permission to it
            with sudo chmod 777 /etc/X11/ -R.

          4. Then I changed the line /usr/sbin/gdm to /usr/sbin/lightdm and the rebooted. By doing this I rolled back the changed from gnome-shell to lightdm, and I saved myself from reinstalling the system.






          share|improve this answer















          Ubuntu actually waits for all the essential drivers and environment application to load before log you in. In my case, I intended to overwrite the default (lightdm unity) with gnome-shell, bit it failed and the boot sequence was waiting infinitely for it to run. So I need to rollback my changes but there isn't much i can do since I cant actually get myself to terminal (the "shift" + boot didn't work).



          Here's what I did to resolve the issue:




          1. Plugged in my usb bootable ubuntu and ran trial version.

          2. Browsed through the bootdrive and edited /etc/X11/default-display-manager.

          3. It didn't allow me to write so I assigned writable permission to it
            with sudo chmod 777 /etc/X11/ -R.

          4. Then I changed the line /usr/sbin/gdm to /usr/sbin/lightdm and the rebooted. By doing this I rolled back the changed from gnome-shell to lightdm, and I saved myself from reinstalling the system.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jun 15 '16 at 17:07

























          answered Jun 15 '16 at 14:54









          Ry VanRy Van

          111




          111













          • you don't need to change the permissions in step 3 -- simply use sudo with your editor to edit the file. this will avoid any future problems caused by incorrect permissions.

            – amc
            Jun 15 '16 at 15:45











          • yea ,i would have but i dont know why,the changes i made with sudo nano never been updated..so i just went to more obvious way of doing it.

            – Ry Van
            Jun 15 '16 at 17:05



















          • you don't need to change the permissions in step 3 -- simply use sudo with your editor to edit the file. this will avoid any future problems caused by incorrect permissions.

            – amc
            Jun 15 '16 at 15:45











          • yea ,i would have but i dont know why,the changes i made with sudo nano never been updated..so i just went to more obvious way of doing it.

            – Ry Van
            Jun 15 '16 at 17:05

















          you don't need to change the permissions in step 3 -- simply use sudo with your editor to edit the file. this will avoid any future problems caused by incorrect permissions.

          – amc
          Jun 15 '16 at 15:45





          you don't need to change the permissions in step 3 -- simply use sudo with your editor to edit the file. this will avoid any future problems caused by incorrect permissions.

          – amc
          Jun 15 '16 at 15:45













          yea ,i would have but i dont know why,the changes i made with sudo nano never been updated..so i just went to more obvious way of doing it.

          – Ry Van
          Jun 15 '16 at 17:05





          yea ,i would have but i dont know why,the changes i made with sudo nano never been updated..so i just went to more obvious way of doing it.

          – Ry Van
          Jun 15 '16 at 17:05


















          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%2f617572%2fubuntu-freezes-during-boot%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