Ubuntu 18.04 stuck at shutdown












22















I am having this weird problem in Ubuntu 18.04. My laptop gets stuck at the shutdown screen every time I use shutdown and I have to manually press the power button for 5 seconds to turn the machine off.



Before 18.04, I was using Ubuntu 16.04 and it never got stuck at shutdown.



Any fix for this?










share|improve this question

























  • Does it freeze on a black screen?

    – YoureSOStubborn
    Apr 28 '18 at 7:03











  • Until the problem is solved it may help with SysRq REISUB. It will reboot the computer gracefully. The corresponding shutdown/poweroff is SysRq REISUO

    – sudodus
    Apr 28 '18 at 7:45








  • 1





    It freezes when it shows ubuntu logo

    – Peter
    Apr 28 '18 at 8:08











  • Have you tried SysRq REISUB or SysRq REISUO yet? In that case, does it help?

    – sudodus
    Apr 28 '18 at 9:08








  • 2





    How long did you wait? I see a 90 second CUPS timeout sometimes on 18.04 shutdown.

    – ubfan1
    Apr 28 '18 at 15:17
















22















I am having this weird problem in Ubuntu 18.04. My laptop gets stuck at the shutdown screen every time I use shutdown and I have to manually press the power button for 5 seconds to turn the machine off.



Before 18.04, I was using Ubuntu 16.04 and it never got stuck at shutdown.



Any fix for this?










share|improve this question

























  • Does it freeze on a black screen?

    – YoureSOStubborn
    Apr 28 '18 at 7:03











  • Until the problem is solved it may help with SysRq REISUB. It will reboot the computer gracefully. The corresponding shutdown/poweroff is SysRq REISUO

    – sudodus
    Apr 28 '18 at 7:45








  • 1





    It freezes when it shows ubuntu logo

    – Peter
    Apr 28 '18 at 8:08











  • Have you tried SysRq REISUB or SysRq REISUO yet? In that case, does it help?

    – sudodus
    Apr 28 '18 at 9:08








  • 2





    How long did you wait? I see a 90 second CUPS timeout sometimes on 18.04 shutdown.

    – ubfan1
    Apr 28 '18 at 15:17














22












22








22


14






I am having this weird problem in Ubuntu 18.04. My laptop gets stuck at the shutdown screen every time I use shutdown and I have to manually press the power button for 5 seconds to turn the machine off.



Before 18.04, I was using Ubuntu 16.04 and it never got stuck at shutdown.



Any fix for this?










share|improve this question
















I am having this weird problem in Ubuntu 18.04. My laptop gets stuck at the shutdown screen every time I use shutdown and I have to manually press the power button for 5 seconds to turn the machine off.



Before 18.04, I was using Ubuntu 16.04 and it never got stuck at shutdown.



Any fix for this?







xubuntu shutdown 18.04






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 23 '18 at 20:19









Zanna

50.6k13136241




50.6k13136241










asked Apr 28 '18 at 4:55









PeterPeter

1352212




1352212













  • Does it freeze on a black screen?

    – YoureSOStubborn
    Apr 28 '18 at 7:03











  • Until the problem is solved it may help with SysRq REISUB. It will reboot the computer gracefully. The corresponding shutdown/poweroff is SysRq REISUO

    – sudodus
    Apr 28 '18 at 7:45








  • 1





    It freezes when it shows ubuntu logo

    – Peter
    Apr 28 '18 at 8:08











  • Have you tried SysRq REISUB or SysRq REISUO yet? In that case, does it help?

    – sudodus
    Apr 28 '18 at 9:08








  • 2





    How long did you wait? I see a 90 second CUPS timeout sometimes on 18.04 shutdown.

    – ubfan1
    Apr 28 '18 at 15:17



















  • Does it freeze on a black screen?

    – YoureSOStubborn
    Apr 28 '18 at 7:03











  • Until the problem is solved it may help with SysRq REISUB. It will reboot the computer gracefully. The corresponding shutdown/poweroff is SysRq REISUO

    – sudodus
    Apr 28 '18 at 7:45








  • 1





    It freezes when it shows ubuntu logo

    – Peter
    Apr 28 '18 at 8:08











  • Have you tried SysRq REISUB or SysRq REISUO yet? In that case, does it help?

    – sudodus
    Apr 28 '18 at 9:08








  • 2





    How long did you wait? I see a 90 second CUPS timeout sometimes on 18.04 shutdown.

    – ubfan1
    Apr 28 '18 at 15:17

















Does it freeze on a black screen?

– YoureSOStubborn
Apr 28 '18 at 7:03





Does it freeze on a black screen?

– YoureSOStubborn
Apr 28 '18 at 7:03













Until the problem is solved it may help with SysRq REISUB. It will reboot the computer gracefully. The corresponding shutdown/poweroff is SysRq REISUO

– sudodus
Apr 28 '18 at 7:45







Until the problem is solved it may help with SysRq REISUB. It will reboot the computer gracefully. The corresponding shutdown/poweroff is SysRq REISUO

– sudodus
Apr 28 '18 at 7:45






1




1





It freezes when it shows ubuntu logo

– Peter
Apr 28 '18 at 8:08





It freezes when it shows ubuntu logo

– Peter
Apr 28 '18 at 8:08













Have you tried SysRq REISUB or SysRq REISUO yet? In that case, does it help?

– sudodus
Apr 28 '18 at 9:08







Have you tried SysRq REISUB or SysRq REISUO yet? In that case, does it help?

– sudodus
Apr 28 '18 at 9:08






2




2





How long did you wait? I see a 90 second CUPS timeout sometimes on 18.04 shutdown.

– ubfan1
Apr 28 '18 at 15:17





How long did you wait? I see a 90 second CUPS timeout sometimes on 18.04 shutdown.

– ubfan1
Apr 28 '18 at 15:17










13 Answers
13






active

oldest

votes


















7














Interestingly, this problems seems to have many fixes/causes. While none of the above helped for me (encountering the same problem), I fixed it by switching from the X.org graphics driver to the propietary nvidia driver that is recommended under software&updates. Since then, reboot works flawlessly.



My setup: Asus G Series Laptop G501VW, with Nvidia 960M graphics card.






share|improve this answer
























  • For me, no solution has worked till now. Whatsoever I tried, I might have to switch back to previous version as this issue has no solution.

    – Peter
    Jun 28 '18 at 5:21











  • I'm using Elementary OS Juno with the same hardware (ASUS ROG G501VW). And I can confirm this solution has solved the problem.

    – frm.adiputra
    Oct 19 '18 at 8:11













  • This one also worked for me - desktop with GeForce GT640. I've switched to nvidia-driver-390.

    – mdob
    Jan 21 at 8:11



















6














Same problem here on my laptop. After some observation, I found out that it has something to do with power saving mode specially automatic suspend.



Go to Settings > Power then turn off all Automatic Suspend options. Also choose Blank screen to Never.



Till Ubuntu team will figure out why suspend mode is interfering with shutdown process, this solved my problem.



Hope this helps






share|improve this answer
























  • I will try this :)

    – Peter
    Jun 2 '18 at 14:37











  • This fixed the problem. Hope ubuntu will send a fix soon

    – Buddhika.Ranaweera
    Sep 6 '18 at 7:40



















2














Had the same problem on a brand new ASUS N705u.
Found had to do with how the video driver installs which causes a conflict with the "secure boot" function of the BIOS.
Solution: Turn the "secure boot" function off until other solution will become available.






share|improve this answer
























  • Do you have any more information, like which video driver causes the problem, and how it causes a problem with secure boot that inhibits shutdown?

    – Hee Jin
    May 8 '18 at 15:44











  • That laptop comes with a NVIDIA GeForce MX150 graphics card. During installation of Ubuntu 18.04 a remark is made that a third party driver is needed which requires safe boot option to be turned off. It also asks for a password to allow safe boot disabling process. However, this password is never being asked for and it appears safe boot remains on regardless. (BIOS -ASUS 302).

    – Karl S.
    May 9 '18 at 23:04













  • Also after initial installation a third party driver "GP107M" is being downloaded and installed. A second computer - same model, that initial question doesn't come up during install once safe boot is disabled in BIOS

    – Karl S.
    May 9 '18 at 23:11






  • 1





    UPDATE: As mentioned above got two new computers with new Kubuntu 18.04 installs. Both kept playing up either on shutdown or then suddenly during the final stages of starting up. - Turns out it's the WIFI Manager ! Turn my WIFI Repeater off - all good. But if it's on those problems are back!

    – Karl S.
    May 10 '18 at 7:35











  • In my case, Wifi router was not even switching off/on even when pressing the Wifi button.

    – Peter
    Jul 9 '18 at 7:19



















2














I had this problem and in my case it seems to be related to the Intel Bay trail CPU which is causing some firmware bugs.



Anyway I have a solution which isn't the best but good enough for now



Solution:





  • Open the terminal and run



    sudo -H gedit /etc/default/grub



  • Edit GRUB_CMDLINE_LINUX_DEFAULT="quite splash" so that it says



    GRUB_CMDLINE_LINUX_DEFAULT="intel_idle.max_cstate=1"



  • Save and exit, and write the changes to GRUB's actual config file:



    sudo update-grub


  • Restart your computer forcefully one last time


Let me know if it worked or when you have a better solution






share|improve this answer


























  • I've been stuck with this for a few months, upgrading to every new kernel, but this finally worked! Thanks.

    – Tihomir Nedev
    Jan 11 at 12:35



















1














Try a couple of sudo reboots from terminal to see if it clears things up:
1st to try, reboot without writing wtmp file:



sudo reboot -d


If that reboots successfully then try your natural close down. If it doesn't reboot, try forced reboot:



sudo reboot -f


If this was an upgrade from 16.04 to 18.04, it may be worth considering a clean install.






share|improve this answer
























  • I will give it a try if it happens again.

    – Peter
    May 1 '18 at 17:53






  • 1





    I had 16.04 (stucking on shutdown) upgraded to 18.04 - the same stuff. <br>Tried clean install of 18.04 - the same problem.

    – R S
    May 15 '18 at 21:50





















1














There are scores of scripts that run when you shutdown. I'm still on 16.04 and for me these are the ones in /etc/rc0.d (which are really links to /etc/init.d). One of them may have a long delay set in what it does for stop.



AFAIK these scripts are run in alphabetical order, so you can insert a few that would just log their execution somewhere, helping you spot where the delay is.






share|improve this answer































    0














    After doing more testing on two computers found it is in fact the Wifi Manager and the way it connects / identifies with the network. On two identical computers the problem disappears once the Wifi manager is turned off. Also tried USB Wifi dongle which worked on one computer but once again caused system to freeze at moment of registration on network. Have already tried a different Wifi manager with improved conditions.
    Also noticed in BIOS if secure boot is disabled then there is a list of drivers rejected bi BIOS due to security issues. Perhaps this is the underlying issue related to the Wifi manager.






    share|improve this answer
























    • Temporary fix: a) Turn Wifi off or b) Try disabling original Wifi Manager and install different one instead.

      – Karl S.
      May 13 '18 at 1:04











    • The unsecure driver theory and wifi makes sense to me. In my case, I installed a modified WiFi driver and since then the problem began. Will be trying disabling secureboot.

      – Rohitt Vashishtha
      May 25 '18 at 7:11



















    0














    I had success turning off usb 3.0 driver in bios, not ideal, but it is fixed until more research is done.






    share|improve this answer































      0














      My system is an older Dell Dimension E521 desktop, dual core, with Lubuntu 18.04, 64-bit.



      In /etc/default/grub, I removed acpi=off and the system started behaving normally.



      More specifically, I changed this:



      GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic acpi=off"


      to:



      GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapci"


      Now my box once again shuts down when I tell it to, and is refreshingly responsive.






      share|improve this answer

































        0














        I noticed that it happens to me too if i use my laptop for more than 10 hours, the gnome-shell uses more memory with time starting from 200 and going up to 500, firefox too starts with memory usage of 150 and goes all the way up to 900, restarting my laptop every 4 to 5 hours solved the issue of shutdown freezing for me I hope it helps you.






        share|improve this answer































          0














          I had the same problem after installing 18.04 on a Fujitsu Scaleo.



          During the install I had to add the acpi=off to be able to install Ubuntu because of a conflict with the Intel 82G33/G31 Express Integrated Graphics Controller.
          After that Ubuntu would just halt at System Halted when I shut it down.



          In the end I changed the BIOS ACPI Suspend Type from S3 to Auto. I did this in Power Management.
          After this the PC would power down and I could even remove the acpi=off from Grub.






          share|improve this answer































            0














            I had similar problem with ubuntu 18.04. I installed nvidia driver and now it works fine. Install your driver as described in https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-18-04-bionic-beaver-linux






            share|improve this answer































              0














              I don't know why but for me, when I remove whole "quite splash acpi=off" and leave it blank, the issue is gone. Now my PC boot and reboot smoothly






              share|improve this answer
























              • Hi! This is truly more of a comment rather than an answer. Your 'fix' is probably the acpi=off part - the quiet suppresses boot messages, and the splash displays a pretty image during boot.

                – Charles Green
                Dec 28 '18 at 16:48











              • Yeah I'm just a newbie. But tried all above solution but it didn't work for me. So I tried remove all three of it and magically it reboot and boot without stuck.

                – Lemaire
                Dec 28 '18 at 18:38











              • Nothing works like success! Why did your system have that boot option set?

                – Charles Green
                Dec 28 '18 at 19:17











              • It is there by default

                – Lemaire
                Dec 30 '18 at 10: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%2f1029068%2fubuntu-18-04-stuck-at-shutdown%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              13 Answers
              13






              active

              oldest

              votes








              13 Answers
              13






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              7














              Interestingly, this problems seems to have many fixes/causes. While none of the above helped for me (encountering the same problem), I fixed it by switching from the X.org graphics driver to the propietary nvidia driver that is recommended under software&updates. Since then, reboot works flawlessly.



              My setup: Asus G Series Laptop G501VW, with Nvidia 960M graphics card.






              share|improve this answer
























              • For me, no solution has worked till now. Whatsoever I tried, I might have to switch back to previous version as this issue has no solution.

                – Peter
                Jun 28 '18 at 5:21











              • I'm using Elementary OS Juno with the same hardware (ASUS ROG G501VW). And I can confirm this solution has solved the problem.

                – frm.adiputra
                Oct 19 '18 at 8:11













              • This one also worked for me - desktop with GeForce GT640. I've switched to nvidia-driver-390.

                – mdob
                Jan 21 at 8:11
















              7














              Interestingly, this problems seems to have many fixes/causes. While none of the above helped for me (encountering the same problem), I fixed it by switching from the X.org graphics driver to the propietary nvidia driver that is recommended under software&updates. Since then, reboot works flawlessly.



              My setup: Asus G Series Laptop G501VW, with Nvidia 960M graphics card.






              share|improve this answer
























              • For me, no solution has worked till now. Whatsoever I tried, I might have to switch back to previous version as this issue has no solution.

                – Peter
                Jun 28 '18 at 5:21











              • I'm using Elementary OS Juno with the same hardware (ASUS ROG G501VW). And I can confirm this solution has solved the problem.

                – frm.adiputra
                Oct 19 '18 at 8:11













              • This one also worked for me - desktop with GeForce GT640. I've switched to nvidia-driver-390.

                – mdob
                Jan 21 at 8:11














              7












              7








              7







              Interestingly, this problems seems to have many fixes/causes. While none of the above helped for me (encountering the same problem), I fixed it by switching from the X.org graphics driver to the propietary nvidia driver that is recommended under software&updates. Since then, reboot works flawlessly.



              My setup: Asus G Series Laptop G501VW, with Nvidia 960M graphics card.






              share|improve this answer













              Interestingly, this problems seems to have many fixes/causes. While none of the above helped for me (encountering the same problem), I fixed it by switching from the X.org graphics driver to the propietary nvidia driver that is recommended under software&updates. Since then, reboot works flawlessly.



              My setup: Asus G Series Laptop G501VW, with Nvidia 960M graphics card.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Jun 26 '18 at 19:41









              RobinRobin

              918




              918













              • For me, no solution has worked till now. Whatsoever I tried, I might have to switch back to previous version as this issue has no solution.

                – Peter
                Jun 28 '18 at 5:21











              • I'm using Elementary OS Juno with the same hardware (ASUS ROG G501VW). And I can confirm this solution has solved the problem.

                – frm.adiputra
                Oct 19 '18 at 8:11













              • This one also worked for me - desktop with GeForce GT640. I've switched to nvidia-driver-390.

                – mdob
                Jan 21 at 8:11



















              • For me, no solution has worked till now. Whatsoever I tried, I might have to switch back to previous version as this issue has no solution.

                – Peter
                Jun 28 '18 at 5:21











              • I'm using Elementary OS Juno with the same hardware (ASUS ROG G501VW). And I can confirm this solution has solved the problem.

                – frm.adiputra
                Oct 19 '18 at 8:11













              • This one also worked for me - desktop with GeForce GT640. I've switched to nvidia-driver-390.

                – mdob
                Jan 21 at 8:11

















              For me, no solution has worked till now. Whatsoever I tried, I might have to switch back to previous version as this issue has no solution.

              – Peter
              Jun 28 '18 at 5:21





              For me, no solution has worked till now. Whatsoever I tried, I might have to switch back to previous version as this issue has no solution.

              – Peter
              Jun 28 '18 at 5:21













              I'm using Elementary OS Juno with the same hardware (ASUS ROG G501VW). And I can confirm this solution has solved the problem.

              – frm.adiputra
              Oct 19 '18 at 8:11







              I'm using Elementary OS Juno with the same hardware (ASUS ROG G501VW). And I can confirm this solution has solved the problem.

              – frm.adiputra
              Oct 19 '18 at 8:11















              This one also worked for me - desktop with GeForce GT640. I've switched to nvidia-driver-390.

              – mdob
              Jan 21 at 8:11





              This one also worked for me - desktop with GeForce GT640. I've switched to nvidia-driver-390.

              – mdob
              Jan 21 at 8:11













              6














              Same problem here on my laptop. After some observation, I found out that it has something to do with power saving mode specially automatic suspend.



              Go to Settings > Power then turn off all Automatic Suspend options. Also choose Blank screen to Never.



              Till Ubuntu team will figure out why suspend mode is interfering with shutdown process, this solved my problem.



              Hope this helps






              share|improve this answer
























              • I will try this :)

                – Peter
                Jun 2 '18 at 14:37











              • This fixed the problem. Hope ubuntu will send a fix soon

                – Buddhika.Ranaweera
                Sep 6 '18 at 7:40
















              6














              Same problem here on my laptop. After some observation, I found out that it has something to do with power saving mode specially automatic suspend.



              Go to Settings > Power then turn off all Automatic Suspend options. Also choose Blank screen to Never.



              Till Ubuntu team will figure out why suspend mode is interfering with shutdown process, this solved my problem.



              Hope this helps






              share|improve this answer
























              • I will try this :)

                – Peter
                Jun 2 '18 at 14:37











              • This fixed the problem. Hope ubuntu will send a fix soon

                – Buddhika.Ranaweera
                Sep 6 '18 at 7:40














              6












              6








              6







              Same problem here on my laptop. After some observation, I found out that it has something to do with power saving mode specially automatic suspend.



              Go to Settings > Power then turn off all Automatic Suspend options. Also choose Blank screen to Never.



              Till Ubuntu team will figure out why suspend mode is interfering with shutdown process, this solved my problem.



              Hope this helps






              share|improve this answer













              Same problem here on my laptop. After some observation, I found out that it has something to do with power saving mode specially automatic suspend.



              Go to Settings > Power then turn off all Automatic Suspend options. Also choose Blank screen to Never.



              Till Ubuntu team will figure out why suspend mode is interfering with shutdown process, this solved my problem.



              Hope this helps







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered May 31 '18 at 19:47









              LaraveldeepLaraveldeep

              1715




              1715













              • I will try this :)

                – Peter
                Jun 2 '18 at 14:37











              • This fixed the problem. Hope ubuntu will send a fix soon

                – Buddhika.Ranaweera
                Sep 6 '18 at 7:40



















              • I will try this :)

                – Peter
                Jun 2 '18 at 14:37











              • This fixed the problem. Hope ubuntu will send a fix soon

                – Buddhika.Ranaweera
                Sep 6 '18 at 7:40

















              I will try this :)

              – Peter
              Jun 2 '18 at 14:37





              I will try this :)

              – Peter
              Jun 2 '18 at 14:37













              This fixed the problem. Hope ubuntu will send a fix soon

              – Buddhika.Ranaweera
              Sep 6 '18 at 7:40





              This fixed the problem. Hope ubuntu will send a fix soon

              – Buddhika.Ranaweera
              Sep 6 '18 at 7:40











              2














              Had the same problem on a brand new ASUS N705u.
              Found had to do with how the video driver installs which causes a conflict with the "secure boot" function of the BIOS.
              Solution: Turn the "secure boot" function off until other solution will become available.






              share|improve this answer
























              • Do you have any more information, like which video driver causes the problem, and how it causes a problem with secure boot that inhibits shutdown?

                – Hee Jin
                May 8 '18 at 15:44











              • That laptop comes with a NVIDIA GeForce MX150 graphics card. During installation of Ubuntu 18.04 a remark is made that a third party driver is needed which requires safe boot option to be turned off. It also asks for a password to allow safe boot disabling process. However, this password is never being asked for and it appears safe boot remains on regardless. (BIOS -ASUS 302).

                – Karl S.
                May 9 '18 at 23:04













              • Also after initial installation a third party driver "GP107M" is being downloaded and installed. A second computer - same model, that initial question doesn't come up during install once safe boot is disabled in BIOS

                – Karl S.
                May 9 '18 at 23:11






              • 1





                UPDATE: As mentioned above got two new computers with new Kubuntu 18.04 installs. Both kept playing up either on shutdown or then suddenly during the final stages of starting up. - Turns out it's the WIFI Manager ! Turn my WIFI Repeater off - all good. But if it's on those problems are back!

                – Karl S.
                May 10 '18 at 7:35











              • In my case, Wifi router was not even switching off/on even when pressing the Wifi button.

                – Peter
                Jul 9 '18 at 7:19
















              2














              Had the same problem on a brand new ASUS N705u.
              Found had to do with how the video driver installs which causes a conflict with the "secure boot" function of the BIOS.
              Solution: Turn the "secure boot" function off until other solution will become available.






              share|improve this answer
























              • Do you have any more information, like which video driver causes the problem, and how it causes a problem with secure boot that inhibits shutdown?

                – Hee Jin
                May 8 '18 at 15:44











              • That laptop comes with a NVIDIA GeForce MX150 graphics card. During installation of Ubuntu 18.04 a remark is made that a third party driver is needed which requires safe boot option to be turned off. It also asks for a password to allow safe boot disabling process. However, this password is never being asked for and it appears safe boot remains on regardless. (BIOS -ASUS 302).

                – Karl S.
                May 9 '18 at 23:04













              • Also after initial installation a third party driver "GP107M" is being downloaded and installed. A second computer - same model, that initial question doesn't come up during install once safe boot is disabled in BIOS

                – Karl S.
                May 9 '18 at 23:11






              • 1





                UPDATE: As mentioned above got two new computers with new Kubuntu 18.04 installs. Both kept playing up either on shutdown or then suddenly during the final stages of starting up. - Turns out it's the WIFI Manager ! Turn my WIFI Repeater off - all good. But if it's on those problems are back!

                – Karl S.
                May 10 '18 at 7:35











              • In my case, Wifi router was not even switching off/on even when pressing the Wifi button.

                – Peter
                Jul 9 '18 at 7:19














              2












              2








              2







              Had the same problem on a brand new ASUS N705u.
              Found had to do with how the video driver installs which causes a conflict with the "secure boot" function of the BIOS.
              Solution: Turn the "secure boot" function off until other solution will become available.






              share|improve this answer













              Had the same problem on a brand new ASUS N705u.
              Found had to do with how the video driver installs which causes a conflict with the "secure boot" function of the BIOS.
              Solution: Turn the "secure boot" function off until other solution will become available.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered May 8 '18 at 9:02









              Karl S.Karl S.

              214




              214













              • Do you have any more information, like which video driver causes the problem, and how it causes a problem with secure boot that inhibits shutdown?

                – Hee Jin
                May 8 '18 at 15:44











              • That laptop comes with a NVIDIA GeForce MX150 graphics card. During installation of Ubuntu 18.04 a remark is made that a third party driver is needed which requires safe boot option to be turned off. It also asks for a password to allow safe boot disabling process. However, this password is never being asked for and it appears safe boot remains on regardless. (BIOS -ASUS 302).

                – Karl S.
                May 9 '18 at 23:04













              • Also after initial installation a third party driver "GP107M" is being downloaded and installed. A second computer - same model, that initial question doesn't come up during install once safe boot is disabled in BIOS

                – Karl S.
                May 9 '18 at 23:11






              • 1





                UPDATE: As mentioned above got two new computers with new Kubuntu 18.04 installs. Both kept playing up either on shutdown or then suddenly during the final stages of starting up. - Turns out it's the WIFI Manager ! Turn my WIFI Repeater off - all good. But if it's on those problems are back!

                – Karl S.
                May 10 '18 at 7:35











              • In my case, Wifi router was not even switching off/on even when pressing the Wifi button.

                – Peter
                Jul 9 '18 at 7:19



















              • Do you have any more information, like which video driver causes the problem, and how it causes a problem with secure boot that inhibits shutdown?

                – Hee Jin
                May 8 '18 at 15:44











              • That laptop comes with a NVIDIA GeForce MX150 graphics card. During installation of Ubuntu 18.04 a remark is made that a third party driver is needed which requires safe boot option to be turned off. It also asks for a password to allow safe boot disabling process. However, this password is never being asked for and it appears safe boot remains on regardless. (BIOS -ASUS 302).

                – Karl S.
                May 9 '18 at 23:04













              • Also after initial installation a third party driver "GP107M" is being downloaded and installed. A second computer - same model, that initial question doesn't come up during install once safe boot is disabled in BIOS

                – Karl S.
                May 9 '18 at 23:11






              • 1





                UPDATE: As mentioned above got two new computers with new Kubuntu 18.04 installs. Both kept playing up either on shutdown or then suddenly during the final stages of starting up. - Turns out it's the WIFI Manager ! Turn my WIFI Repeater off - all good. But if it's on those problems are back!

                – Karl S.
                May 10 '18 at 7:35











              • In my case, Wifi router was not even switching off/on even when pressing the Wifi button.

                – Peter
                Jul 9 '18 at 7:19

















              Do you have any more information, like which video driver causes the problem, and how it causes a problem with secure boot that inhibits shutdown?

              – Hee Jin
              May 8 '18 at 15:44





              Do you have any more information, like which video driver causes the problem, and how it causes a problem with secure boot that inhibits shutdown?

              – Hee Jin
              May 8 '18 at 15:44













              That laptop comes with a NVIDIA GeForce MX150 graphics card. During installation of Ubuntu 18.04 a remark is made that a third party driver is needed which requires safe boot option to be turned off. It also asks for a password to allow safe boot disabling process. However, this password is never being asked for and it appears safe boot remains on regardless. (BIOS -ASUS 302).

              – Karl S.
              May 9 '18 at 23:04







              That laptop comes with a NVIDIA GeForce MX150 graphics card. During installation of Ubuntu 18.04 a remark is made that a third party driver is needed which requires safe boot option to be turned off. It also asks for a password to allow safe boot disabling process. However, this password is never being asked for and it appears safe boot remains on regardless. (BIOS -ASUS 302).

              – Karl S.
              May 9 '18 at 23:04















              Also after initial installation a third party driver "GP107M" is being downloaded and installed. A second computer - same model, that initial question doesn't come up during install once safe boot is disabled in BIOS

              – Karl S.
              May 9 '18 at 23:11





              Also after initial installation a third party driver "GP107M" is being downloaded and installed. A second computer - same model, that initial question doesn't come up during install once safe boot is disabled in BIOS

              – Karl S.
              May 9 '18 at 23:11




              1




              1





              UPDATE: As mentioned above got two new computers with new Kubuntu 18.04 installs. Both kept playing up either on shutdown or then suddenly during the final stages of starting up. - Turns out it's the WIFI Manager ! Turn my WIFI Repeater off - all good. But if it's on those problems are back!

              – Karl S.
              May 10 '18 at 7:35





              UPDATE: As mentioned above got two new computers with new Kubuntu 18.04 installs. Both kept playing up either on shutdown or then suddenly during the final stages of starting up. - Turns out it's the WIFI Manager ! Turn my WIFI Repeater off - all good. But if it's on those problems are back!

              – Karl S.
              May 10 '18 at 7:35













              In my case, Wifi router was not even switching off/on even when pressing the Wifi button.

              – Peter
              Jul 9 '18 at 7:19





              In my case, Wifi router was not even switching off/on even when pressing the Wifi button.

              – Peter
              Jul 9 '18 at 7:19











              2














              I had this problem and in my case it seems to be related to the Intel Bay trail CPU which is causing some firmware bugs.



              Anyway I have a solution which isn't the best but good enough for now



              Solution:





              • Open the terminal and run



                sudo -H gedit /etc/default/grub



              • Edit GRUB_CMDLINE_LINUX_DEFAULT="quite splash" so that it says



                GRUB_CMDLINE_LINUX_DEFAULT="intel_idle.max_cstate=1"



              • Save and exit, and write the changes to GRUB's actual config file:



                sudo update-grub


              • Restart your computer forcefully one last time


              Let me know if it worked or when you have a better solution






              share|improve this answer


























              • I've been stuck with this for a few months, upgrading to every new kernel, but this finally worked! Thanks.

                – Tihomir Nedev
                Jan 11 at 12:35
















              2














              I had this problem and in my case it seems to be related to the Intel Bay trail CPU which is causing some firmware bugs.



              Anyway I have a solution which isn't the best but good enough for now



              Solution:





              • Open the terminal and run



                sudo -H gedit /etc/default/grub



              • Edit GRUB_CMDLINE_LINUX_DEFAULT="quite splash" so that it says



                GRUB_CMDLINE_LINUX_DEFAULT="intel_idle.max_cstate=1"



              • Save and exit, and write the changes to GRUB's actual config file:



                sudo update-grub


              • Restart your computer forcefully one last time


              Let me know if it worked or when you have a better solution






              share|improve this answer


























              • I've been stuck with this for a few months, upgrading to every new kernel, but this finally worked! Thanks.

                – Tihomir Nedev
                Jan 11 at 12:35














              2












              2








              2







              I had this problem and in my case it seems to be related to the Intel Bay trail CPU which is causing some firmware bugs.



              Anyway I have a solution which isn't the best but good enough for now



              Solution:





              • Open the terminal and run



                sudo -H gedit /etc/default/grub



              • Edit GRUB_CMDLINE_LINUX_DEFAULT="quite splash" so that it says



                GRUB_CMDLINE_LINUX_DEFAULT="intel_idle.max_cstate=1"



              • Save and exit, and write the changes to GRUB's actual config file:



                sudo update-grub


              • Restart your computer forcefully one last time


              Let me know if it worked or when you have a better solution






              share|improve this answer















              I had this problem and in my case it seems to be related to the Intel Bay trail CPU which is causing some firmware bugs.



              Anyway I have a solution which isn't the best but good enough for now



              Solution:





              • Open the terminal and run



                sudo -H gedit /etc/default/grub



              • Edit GRUB_CMDLINE_LINUX_DEFAULT="quite splash" so that it says



                GRUB_CMDLINE_LINUX_DEFAULT="intel_idle.max_cstate=1"



              • Save and exit, and write the changes to GRUB's actual config file:



                sudo update-grub


              • Restart your computer forcefully one last time


              Let me know if it worked or when you have a better solution







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited 10 hours ago









              Zanna

              50.6k13136241




              50.6k13136241










              answered Sep 9 '18 at 7:02









              Sunny RaySunny Ray

              465




              465













              • I've been stuck with this for a few months, upgrading to every new kernel, but this finally worked! Thanks.

                – Tihomir Nedev
                Jan 11 at 12:35



















              • I've been stuck with this for a few months, upgrading to every new kernel, but this finally worked! Thanks.

                – Tihomir Nedev
                Jan 11 at 12:35

















              I've been stuck with this for a few months, upgrading to every new kernel, but this finally worked! Thanks.

              – Tihomir Nedev
              Jan 11 at 12:35





              I've been stuck with this for a few months, upgrading to every new kernel, but this finally worked! Thanks.

              – Tihomir Nedev
              Jan 11 at 12:35











              1














              Try a couple of sudo reboots from terminal to see if it clears things up:
              1st to try, reboot without writing wtmp file:



              sudo reboot -d


              If that reboots successfully then try your natural close down. If it doesn't reboot, try forced reboot:



              sudo reboot -f


              If this was an upgrade from 16.04 to 18.04, it may be worth considering a clean install.






              share|improve this answer
























              • I will give it a try if it happens again.

                – Peter
                May 1 '18 at 17:53






              • 1





                I had 16.04 (stucking on shutdown) upgraded to 18.04 - the same stuff. <br>Tried clean install of 18.04 - the same problem.

                – R S
                May 15 '18 at 21:50


















              1














              Try a couple of sudo reboots from terminal to see if it clears things up:
              1st to try, reboot without writing wtmp file:



              sudo reboot -d


              If that reboots successfully then try your natural close down. If it doesn't reboot, try forced reboot:



              sudo reboot -f


              If this was an upgrade from 16.04 to 18.04, it may be worth considering a clean install.






              share|improve this answer
























              • I will give it a try if it happens again.

                – Peter
                May 1 '18 at 17:53






              • 1





                I had 16.04 (stucking on shutdown) upgraded to 18.04 - the same stuff. <br>Tried clean install of 18.04 - the same problem.

                – R S
                May 15 '18 at 21:50
















              1












              1








              1







              Try a couple of sudo reboots from terminal to see if it clears things up:
              1st to try, reboot without writing wtmp file:



              sudo reboot -d


              If that reboots successfully then try your natural close down. If it doesn't reboot, try forced reboot:



              sudo reboot -f


              If this was an upgrade from 16.04 to 18.04, it may be worth considering a clean install.






              share|improve this answer













              Try a couple of sudo reboots from terminal to see if it clears things up:
              1st to try, reboot without writing wtmp file:



              sudo reboot -d


              If that reboots successfully then try your natural close down. If it doesn't reboot, try forced reboot:



              sudo reboot -f


              If this was an upgrade from 16.04 to 18.04, it may be worth considering a clean install.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Apr 29 '18 at 7:22









              BroadswordeBroadsworde

              9371822




              9371822













              • I will give it a try if it happens again.

                – Peter
                May 1 '18 at 17:53






              • 1





                I had 16.04 (stucking on shutdown) upgraded to 18.04 - the same stuff. <br>Tried clean install of 18.04 - the same problem.

                – R S
                May 15 '18 at 21:50





















              • I will give it a try if it happens again.

                – Peter
                May 1 '18 at 17:53






              • 1





                I had 16.04 (stucking on shutdown) upgraded to 18.04 - the same stuff. <br>Tried clean install of 18.04 - the same problem.

                – R S
                May 15 '18 at 21:50



















              I will give it a try if it happens again.

              – Peter
              May 1 '18 at 17:53





              I will give it a try if it happens again.

              – Peter
              May 1 '18 at 17:53




              1




              1





              I had 16.04 (stucking on shutdown) upgraded to 18.04 - the same stuff. <br>Tried clean install of 18.04 - the same problem.

              – R S
              May 15 '18 at 21:50







              I had 16.04 (stucking on shutdown) upgraded to 18.04 - the same stuff. <br>Tried clean install of 18.04 - the same problem.

              – R S
              May 15 '18 at 21:50













              1














              There are scores of scripts that run when you shutdown. I'm still on 16.04 and for me these are the ones in /etc/rc0.d (which are really links to /etc/init.d). One of them may have a long delay set in what it does for stop.



              AFAIK these scripts are run in alphabetical order, so you can insert a few that would just log their execution somewhere, helping you spot where the delay is.






              share|improve this answer




























                1














                There are scores of scripts that run when you shutdown. I'm still on 16.04 and for me these are the ones in /etc/rc0.d (which are really links to /etc/init.d). One of them may have a long delay set in what it does for stop.



                AFAIK these scripts are run in alphabetical order, so you can insert a few that would just log their execution somewhere, helping you spot where the delay is.






                share|improve this answer


























                  1












                  1








                  1







                  There are scores of scripts that run when you shutdown. I'm still on 16.04 and for me these are the ones in /etc/rc0.d (which are really links to /etc/init.d). One of them may have a long delay set in what it does for stop.



                  AFAIK these scripts are run in alphabetical order, so you can insert a few that would just log their execution somewhere, helping you spot where the delay is.






                  share|improve this answer













                  There are scores of scripts that run when you shutdown. I'm still on 16.04 and for me these are the ones in /etc/rc0.d (which are really links to /etc/init.d). One of them may have a long delay set in what it does for stop.



                  AFAIK these scripts are run in alphabetical order, so you can insert a few that would just log their execution somewhere, helping you spot where the delay is.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Apr 29 '18 at 7:45









                  xenoidxenoid

                  1,6181416




                  1,6181416























                      0














                      After doing more testing on two computers found it is in fact the Wifi Manager and the way it connects / identifies with the network. On two identical computers the problem disappears once the Wifi manager is turned off. Also tried USB Wifi dongle which worked on one computer but once again caused system to freeze at moment of registration on network. Have already tried a different Wifi manager with improved conditions.
                      Also noticed in BIOS if secure boot is disabled then there is a list of drivers rejected bi BIOS due to security issues. Perhaps this is the underlying issue related to the Wifi manager.






                      share|improve this answer
























                      • Temporary fix: a) Turn Wifi off or b) Try disabling original Wifi Manager and install different one instead.

                        – Karl S.
                        May 13 '18 at 1:04











                      • The unsecure driver theory and wifi makes sense to me. In my case, I installed a modified WiFi driver and since then the problem began. Will be trying disabling secureboot.

                        – Rohitt Vashishtha
                        May 25 '18 at 7:11
















                      0














                      After doing more testing on two computers found it is in fact the Wifi Manager and the way it connects / identifies with the network. On two identical computers the problem disappears once the Wifi manager is turned off. Also tried USB Wifi dongle which worked on one computer but once again caused system to freeze at moment of registration on network. Have already tried a different Wifi manager with improved conditions.
                      Also noticed in BIOS if secure boot is disabled then there is a list of drivers rejected bi BIOS due to security issues. Perhaps this is the underlying issue related to the Wifi manager.






                      share|improve this answer
























                      • Temporary fix: a) Turn Wifi off or b) Try disabling original Wifi Manager and install different one instead.

                        – Karl S.
                        May 13 '18 at 1:04











                      • The unsecure driver theory and wifi makes sense to me. In my case, I installed a modified WiFi driver and since then the problem began. Will be trying disabling secureboot.

                        – Rohitt Vashishtha
                        May 25 '18 at 7:11














                      0












                      0








                      0







                      After doing more testing on two computers found it is in fact the Wifi Manager and the way it connects / identifies with the network. On two identical computers the problem disappears once the Wifi manager is turned off. Also tried USB Wifi dongle which worked on one computer but once again caused system to freeze at moment of registration on network. Have already tried a different Wifi manager with improved conditions.
                      Also noticed in BIOS if secure boot is disabled then there is a list of drivers rejected bi BIOS due to security issues. Perhaps this is the underlying issue related to the Wifi manager.






                      share|improve this answer













                      After doing more testing on two computers found it is in fact the Wifi Manager and the way it connects / identifies with the network. On two identical computers the problem disappears once the Wifi manager is turned off. Also tried USB Wifi dongle which worked on one computer but once again caused system to freeze at moment of registration on network. Have already tried a different Wifi manager with improved conditions.
                      Also noticed in BIOS if secure boot is disabled then there is a list of drivers rejected bi BIOS due to security issues. Perhaps this is the underlying issue related to the Wifi manager.







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered May 13 '18 at 1:01









                      Karl S.Karl S.

                      214




                      214













                      • Temporary fix: a) Turn Wifi off or b) Try disabling original Wifi Manager and install different one instead.

                        – Karl S.
                        May 13 '18 at 1:04











                      • The unsecure driver theory and wifi makes sense to me. In my case, I installed a modified WiFi driver and since then the problem began. Will be trying disabling secureboot.

                        – Rohitt Vashishtha
                        May 25 '18 at 7:11



















                      • Temporary fix: a) Turn Wifi off or b) Try disabling original Wifi Manager and install different one instead.

                        – Karl S.
                        May 13 '18 at 1:04











                      • The unsecure driver theory and wifi makes sense to me. In my case, I installed a modified WiFi driver and since then the problem began. Will be trying disabling secureboot.

                        – Rohitt Vashishtha
                        May 25 '18 at 7:11

















                      Temporary fix: a) Turn Wifi off or b) Try disabling original Wifi Manager and install different one instead.

                      – Karl S.
                      May 13 '18 at 1:04





                      Temporary fix: a) Turn Wifi off or b) Try disabling original Wifi Manager and install different one instead.

                      – Karl S.
                      May 13 '18 at 1:04













                      The unsecure driver theory and wifi makes sense to me. In my case, I installed a modified WiFi driver and since then the problem began. Will be trying disabling secureboot.

                      – Rohitt Vashishtha
                      May 25 '18 at 7:11





                      The unsecure driver theory and wifi makes sense to me. In my case, I installed a modified WiFi driver and since then the problem began. Will be trying disabling secureboot.

                      – Rohitt Vashishtha
                      May 25 '18 at 7:11











                      0














                      I had success turning off usb 3.0 driver in bios, not ideal, but it is fixed until more research is done.






                      share|improve this answer




























                        0














                        I had success turning off usb 3.0 driver in bios, not ideal, but it is fixed until more research is done.






                        share|improve this answer


























                          0












                          0








                          0







                          I had success turning off usb 3.0 driver in bios, not ideal, but it is fixed until more research is done.






                          share|improve this answer













                          I had success turning off usb 3.0 driver in bios, not ideal, but it is fixed until more research is done.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Aug 20 '18 at 0:51









                          user861985user861985

                          1




                          1























                              0














                              My system is an older Dell Dimension E521 desktop, dual core, with Lubuntu 18.04, 64-bit.



                              In /etc/default/grub, I removed acpi=off and the system started behaving normally.



                              More specifically, I changed this:



                              GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic acpi=off"


                              to:



                              GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapci"


                              Now my box once again shuts down when I tell it to, and is refreshingly responsive.






                              share|improve this answer






























                                0














                                My system is an older Dell Dimension E521 desktop, dual core, with Lubuntu 18.04, 64-bit.



                                In /etc/default/grub, I removed acpi=off and the system started behaving normally.



                                More specifically, I changed this:



                                GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic acpi=off"


                                to:



                                GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapci"


                                Now my box once again shuts down when I tell it to, and is refreshingly responsive.






                                share|improve this answer




























                                  0












                                  0








                                  0







                                  My system is an older Dell Dimension E521 desktop, dual core, with Lubuntu 18.04, 64-bit.



                                  In /etc/default/grub, I removed acpi=off and the system started behaving normally.



                                  More specifically, I changed this:



                                  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic acpi=off"


                                  to:



                                  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapci"


                                  Now my box once again shuts down when I tell it to, and is refreshingly responsive.






                                  share|improve this answer















                                  My system is an older Dell Dimension E521 desktop, dual core, with Lubuntu 18.04, 64-bit.



                                  In /etc/default/grub, I removed acpi=off and the system started behaving normally.



                                  More specifically, I changed this:



                                  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic acpi=off"


                                  to:



                                  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapci"


                                  Now my box once again shuts down when I tell it to, and is refreshingly responsive.







                                  share|improve this answer














                                  share|improve this answer



                                  share|improve this answer








                                  edited Aug 27 '18 at 7:56









                                  Fabby

                                  26.8k1360161




                                  26.8k1360161










                                  answered Aug 26 '18 at 16:09









                                  27855282785528

                                  1012




                                  1012























                                      0














                                      I noticed that it happens to me too if i use my laptop for more than 10 hours, the gnome-shell uses more memory with time starting from 200 and going up to 500, firefox too starts with memory usage of 150 and goes all the way up to 900, restarting my laptop every 4 to 5 hours solved the issue of shutdown freezing for me I hope it helps you.






                                      share|improve this answer




























                                        0














                                        I noticed that it happens to me too if i use my laptop for more than 10 hours, the gnome-shell uses more memory with time starting from 200 and going up to 500, firefox too starts with memory usage of 150 and goes all the way up to 900, restarting my laptop every 4 to 5 hours solved the issue of shutdown freezing for me I hope it helps you.






                                        share|improve this answer


























                                          0












                                          0








                                          0







                                          I noticed that it happens to me too if i use my laptop for more than 10 hours, the gnome-shell uses more memory with time starting from 200 and going up to 500, firefox too starts with memory usage of 150 and goes all the way up to 900, restarting my laptop every 4 to 5 hours solved the issue of shutdown freezing for me I hope it helps you.






                                          share|improve this answer













                                          I noticed that it happens to me too if i use my laptop for more than 10 hours, the gnome-shell uses more memory with time starting from 200 and going up to 500, firefox too starts with memory usage of 150 and goes all the way up to 900, restarting my laptop every 4 to 5 hours solved the issue of shutdown freezing for me I hope it helps you.







                                          share|improve this answer












                                          share|improve this answer



                                          share|improve this answer










                                          answered Sep 9 '18 at 7:38









                                          Kashmir PanKashmir Pan

                                          15




                                          15























                                              0














                                              I had the same problem after installing 18.04 on a Fujitsu Scaleo.



                                              During the install I had to add the acpi=off to be able to install Ubuntu because of a conflict with the Intel 82G33/G31 Express Integrated Graphics Controller.
                                              After that Ubuntu would just halt at System Halted when I shut it down.



                                              In the end I changed the BIOS ACPI Suspend Type from S3 to Auto. I did this in Power Management.
                                              After this the PC would power down and I could even remove the acpi=off from Grub.






                                              share|improve this answer




























                                                0














                                                I had the same problem after installing 18.04 on a Fujitsu Scaleo.



                                                During the install I had to add the acpi=off to be able to install Ubuntu because of a conflict with the Intel 82G33/G31 Express Integrated Graphics Controller.
                                                After that Ubuntu would just halt at System Halted when I shut it down.



                                                In the end I changed the BIOS ACPI Suspend Type from S3 to Auto. I did this in Power Management.
                                                After this the PC would power down and I could even remove the acpi=off from Grub.






                                                share|improve this answer


























                                                  0












                                                  0








                                                  0







                                                  I had the same problem after installing 18.04 on a Fujitsu Scaleo.



                                                  During the install I had to add the acpi=off to be able to install Ubuntu because of a conflict with the Intel 82G33/G31 Express Integrated Graphics Controller.
                                                  After that Ubuntu would just halt at System Halted when I shut it down.



                                                  In the end I changed the BIOS ACPI Suspend Type from S3 to Auto. I did this in Power Management.
                                                  After this the PC would power down and I could even remove the acpi=off from Grub.






                                                  share|improve this answer













                                                  I had the same problem after installing 18.04 on a Fujitsu Scaleo.



                                                  During the install I had to add the acpi=off to be able to install Ubuntu because of a conflict with the Intel 82G33/G31 Express Integrated Graphics Controller.
                                                  After that Ubuntu would just halt at System Halted when I shut it down.



                                                  In the end I changed the BIOS ACPI Suspend Type from S3 to Auto. I did this in Power Management.
                                                  After this the PC would power down and I could even remove the acpi=off from Grub.







                                                  share|improve this answer












                                                  share|improve this answer



                                                  share|improve this answer










                                                  answered Nov 22 '18 at 22:42









                                                  MattijsMattijs

                                                  4818




                                                  4818























                                                      0














                                                      I had similar problem with ubuntu 18.04. I installed nvidia driver and now it works fine. Install your driver as described in https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-18-04-bionic-beaver-linux






                                                      share|improve this answer




























                                                        0














                                                        I had similar problem with ubuntu 18.04. I installed nvidia driver and now it works fine. Install your driver as described in https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-18-04-bionic-beaver-linux






                                                        share|improve this answer


























                                                          0












                                                          0








                                                          0







                                                          I had similar problem with ubuntu 18.04. I installed nvidia driver and now it works fine. Install your driver as described in https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-18-04-bionic-beaver-linux






                                                          share|improve this answer













                                                          I had similar problem with ubuntu 18.04. I installed nvidia driver and now it works fine. Install your driver as described in https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-18-04-bionic-beaver-linux







                                                          share|improve this answer












                                                          share|improve this answer



                                                          share|improve this answer










                                                          answered Dec 13 '18 at 20:44









                                                          Seyed Morteza MousaviSeyed Morteza Mousavi

                                                          10816




                                                          10816























                                                              0














                                                              I don't know why but for me, when I remove whole "quite splash acpi=off" and leave it blank, the issue is gone. Now my PC boot and reboot smoothly






                                                              share|improve this answer
























                                                              • Hi! This is truly more of a comment rather than an answer. Your 'fix' is probably the acpi=off part - the quiet suppresses boot messages, and the splash displays a pretty image during boot.

                                                                – Charles Green
                                                                Dec 28 '18 at 16:48











                                                              • Yeah I'm just a newbie. But tried all above solution but it didn't work for me. So I tried remove all three of it and magically it reboot and boot without stuck.

                                                                – Lemaire
                                                                Dec 28 '18 at 18:38











                                                              • Nothing works like success! Why did your system have that boot option set?

                                                                – Charles Green
                                                                Dec 28 '18 at 19:17











                                                              • It is there by default

                                                                – Lemaire
                                                                Dec 30 '18 at 10:05
















                                                              0














                                                              I don't know why but for me, when I remove whole "quite splash acpi=off" and leave it blank, the issue is gone. Now my PC boot and reboot smoothly






                                                              share|improve this answer
























                                                              • Hi! This is truly more of a comment rather than an answer. Your 'fix' is probably the acpi=off part - the quiet suppresses boot messages, and the splash displays a pretty image during boot.

                                                                – Charles Green
                                                                Dec 28 '18 at 16:48











                                                              • Yeah I'm just a newbie. But tried all above solution but it didn't work for me. So I tried remove all three of it and magically it reboot and boot without stuck.

                                                                – Lemaire
                                                                Dec 28 '18 at 18:38











                                                              • Nothing works like success! Why did your system have that boot option set?

                                                                – Charles Green
                                                                Dec 28 '18 at 19:17











                                                              • It is there by default

                                                                – Lemaire
                                                                Dec 30 '18 at 10:05














                                                              0












                                                              0








                                                              0







                                                              I don't know why but for me, when I remove whole "quite splash acpi=off" and leave it blank, the issue is gone. Now my PC boot and reboot smoothly






                                                              share|improve this answer













                                                              I don't know why but for me, when I remove whole "quite splash acpi=off" and leave it blank, the issue is gone. Now my PC boot and reboot smoothly







                                                              share|improve this answer












                                                              share|improve this answer



                                                              share|improve this answer










                                                              answered Dec 28 '18 at 16:01









                                                              LemaireLemaire

                                                              1




                                                              1













                                                              • Hi! This is truly more of a comment rather than an answer. Your 'fix' is probably the acpi=off part - the quiet suppresses boot messages, and the splash displays a pretty image during boot.

                                                                – Charles Green
                                                                Dec 28 '18 at 16:48











                                                              • Yeah I'm just a newbie. But tried all above solution but it didn't work for me. So I tried remove all three of it and magically it reboot and boot without stuck.

                                                                – Lemaire
                                                                Dec 28 '18 at 18:38











                                                              • Nothing works like success! Why did your system have that boot option set?

                                                                – Charles Green
                                                                Dec 28 '18 at 19:17











                                                              • It is there by default

                                                                – Lemaire
                                                                Dec 30 '18 at 10:05



















                                                              • Hi! This is truly more of a comment rather than an answer. Your 'fix' is probably the acpi=off part - the quiet suppresses boot messages, and the splash displays a pretty image during boot.

                                                                – Charles Green
                                                                Dec 28 '18 at 16:48











                                                              • Yeah I'm just a newbie. But tried all above solution but it didn't work for me. So I tried remove all three of it and magically it reboot and boot without stuck.

                                                                – Lemaire
                                                                Dec 28 '18 at 18:38











                                                              • Nothing works like success! Why did your system have that boot option set?

                                                                – Charles Green
                                                                Dec 28 '18 at 19:17











                                                              • It is there by default

                                                                – Lemaire
                                                                Dec 30 '18 at 10:05

















                                                              Hi! This is truly more of a comment rather than an answer. Your 'fix' is probably the acpi=off part - the quiet suppresses boot messages, and the splash displays a pretty image during boot.

                                                              – Charles Green
                                                              Dec 28 '18 at 16:48





                                                              Hi! This is truly more of a comment rather than an answer. Your 'fix' is probably the acpi=off part - the quiet suppresses boot messages, and the splash displays a pretty image during boot.

                                                              – Charles Green
                                                              Dec 28 '18 at 16:48













                                                              Yeah I'm just a newbie. But tried all above solution but it didn't work for me. So I tried remove all three of it and magically it reboot and boot without stuck.

                                                              – Lemaire
                                                              Dec 28 '18 at 18:38





                                                              Yeah I'm just a newbie. But tried all above solution but it didn't work for me. So I tried remove all three of it and magically it reboot and boot without stuck.

                                                              – Lemaire
                                                              Dec 28 '18 at 18:38













                                                              Nothing works like success! Why did your system have that boot option set?

                                                              – Charles Green
                                                              Dec 28 '18 at 19:17





                                                              Nothing works like success! Why did your system have that boot option set?

                                                              – Charles Green
                                                              Dec 28 '18 at 19:17













                                                              It is there by default

                                                              – Lemaire
                                                              Dec 30 '18 at 10:05





                                                              It is there by default

                                                              – Lemaire
                                                              Dec 30 '18 at 10: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%2f1029068%2fubuntu-18-04-stuck-at-shutdown%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

                                                              數位音樂下載

                                                              When can things happen in Etherscan, such as the picture below?

                                                              格利澤436b