Poweroff or reboot hangs. Laptop won't shutdown. 16.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Confirmed
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off.
I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end.
The issue seems to affect lately quite many users as shown by the google results of the past month / week or so.
I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred.
Unmounting the swap as suggested online doesn't work.
Also rebooting the system is not working either due to the same issue.
So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously.
Reproducible: Always
Steps to Reproduce:
1.Install OS
2.Do something, anything or nothing
3.Try to shutdown or reboot
Actual Results:
The computer is not shutting down: "Reached target shutdown" and hangs there.
Expected Results:
Powering off the machine.
For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Elio (eliodisegno) wrote : | #1 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Launchpad Janitor (janitor) wrote : | #2 |
Changed in systemd (Ubuntu): | |
status: | New → Confirmed |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Willem Pieter Groeneveld (limsgroen) wrote : | #3 |
exactly the same here on my compaq presario c500
Changed in systemd (Ubuntu): | |
importance: | Undecided → High |
importance: | High → Critical |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
jtarin (jtarin) wrote : | #4 |
Same here
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Don Nadie (don.nadie) wrote : | #5 |
Just want to say I have the same problem.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
jtarin (jtarin) wrote : | #6 |
I solved this in my situation by adding the term "acpi=force" to the "GRUB_CMDLINE_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
jtarin (jtarin) wrote : | #7 |
In my situation I solved the problem by editing my Grub configuration.
GRUB_CMDLINE_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
damiano (damiano1996) wrote : | #8 |
I have the same problem with a notebook asus f402sa and I couldn't resolve it neither editing the grub configuration as you said.
Changed in systemd (Ubuntu): | |
assignee: | nobody → damiano (damiano1996) |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
sciasbat (fabio-forno) wrote : | #9 |
Same bug with an asus x540s
affects: | systemd (Ubuntu) → linux (Ubuntu) |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Elio (eliodisegno) wrote : | #10 |
After the last update my asus x540sa notebook seems to shut down and restart properly. Closing the lid still doesn't suspend the system though.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #11 |
Does this bug still exist for folks after applying the latest updates as Elio did in comment #10?
Changed in linux (Ubuntu): | |
importance: | Critical → High |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
jtarin (jtarin) wrote : | #12 |
I'm still having the problem even after all current updates.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
sciasbat (fabio-forno) wrote : | #13 |
Fot me it's fixed with the latest update. Still very slow, you need need to wait up to 1 minute for the shutdown, but it works
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Tari (tari-sk) wrote : | #14 |
After yesterday update still not working for me. System still stuck on poweroff.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Michael Yarv (mixa-poison) wrote : | #15 |
Hello,
I have exact the same problem with ASUS notebook.
Is there any quick fix for it?
GRUB_CMDLINE_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
francis (a-c-f) wrote : | #16 |
Hi, same problem here. I have lenovo yoga 500....
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Tari (tari-sk) wrote : | #17 |
When can we expect the FIX???
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Andrew Smith (z-andrew-4) wrote : | #18 |
I run LTS releases and ran into this Shutdown failure about the time the upgrade notification came through from 14.04, so did not investigate closely as I suspected it would go when I upgraded to 16.04. It didn't. Mine is a pretty standard i7 desktop with an SSD. I have noticed the following:
*When it fails I can either Suspend it or pop up a terminal and do "shutdown -h now". Both work immediately but,
*If Suspend is used, the following time I can do a normal Shutdown and it works normally. The normal Shutdown after that fails.
*If the terminal command is used, the following time I do a normal Shutdown it fails.
So somehow Suspend circumvents the problem for one time. I am no command line guru so I don't know what logs or files I should be looking at. Any suggestions?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jakub T. Jankiewicz (jcubic) wrote : | #19 |
I have similar problem but only reboot is not working and it hangs after display is turn off, the keyboard is highlighted but it don't respond to keyboard brightness buttons.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Thomas Franke (t-aus-o) wrote : | #20 |
Again: When can we expect a FIX???
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
VinDSL (perfect-pecker) wrote : | #21 |
Ran into this problem on my Dell 7010 i5 desktop machine, after doing a fresh 16.10 install -- first time it's happened with any OS that I've run on it.
In my case, I'm getting DRDY ERRs on shutdown/restart. Hangs for several minutes with my SSD activity light lit up solid. Eventually the errors time out, and it shuts down, but it's a painfully long process.
I downgraded the kernel to 4.4.x for shiggles. The LTS enablement stack, graphic stack, and so forth were foobar, of course, but it otherwise booted and shutdown normally.
It smells like a kernel bug, to me, at this point. I'll investigate further and post back, if I can put a finger on it.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Blackbug (blackbug-nx) wrote : | #22 |
I am also facing the issue since a week. I upgraded few libs and installed xcfe DE on kubuntu and started having this issue. I have tried to modify the grub as well by adding the acpi line but doesnt help.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
VinDSL (perfect-pecker) wrote : | #23 |
UPDATE: I'm more convinced than ever, that this is a kernel bug.
I multi-booted the following 64-bit distros on my Dell 7010 i5-3470:
Ubuntu 16.10 Yakkety Yak, Linux Kernel 4.8.x (as described above)
openSUSE Tumbleweed, Linux Kernel 4.8.x (same problem)
Peppermint 7, Linux Kernel 4.4.x (no problems)
As an aside:
Windows 10 Pro (no problems)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Blackbug (blackbug-nx) wrote : | #24 |
If I switch to runlevel 2,3 or 4 and then shutdown it successfully shutsoff.
This bug is seriously annoying now. I damaged my filesystem because of frequent improper shutdown.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
jtarin (jtarin) wrote : Re: [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 | #25 |
So is the only solution kernel regression?
On Nov 3, 2016 7:35 AM, "Blackbug" <email address hidden> wrote:
> If I switch to runlevel 2,3 or 4 and then shutdown it successfully
> shutsoff.
>
> This bug is seriously annoying now. I damaged my filesystem because of
> frequent improper shutdown.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Poweroff or reboot hangs. Laptop won't shutdown. 16.04
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> This is about a fresh Ubuntu 16.04 install on a new laptop (asus
> x540sa). After pressing the shutdown button in the start menu; the
> shutdown procedure starts and in the final splash screen the system
> just hangs. Tried a second time by pressing Esc once the splash screen
> showed up and I saw that it reaches the line "Reached target shutdown"
> and just stops there, no matter how long I leave it there the machine
> won't turn off.
>
> I also tried a Kubuntu 16.04 fresh install on the same machine and it
> hanged too at the final splash screen where the pulsating logo
> stopped. Then I tried with Esc only to see the exact same line in the
> end.
>
> The issue seems to affect lately quite many users as shown by the
> google results of the past month / week or so.
>
> I have also tried shutting down from the console with shutdown -and
> all the parameters after that suggested online- and sudo poweroff but
> unfortunately they didn't do the trick. The exact same situation
> occurred.
>
> Unmounting the swap as suggested online doesn't work.
>
> Also rebooting the system is not working either due to the same issue.
>
> So right now the only way for me to poweroff the machine is to press
> the power button on the keyboard continuously.
>
> Reproducible: Always
>
> Steps to Reproduce:
> 1.Install OS
> 2.Do something, anything or nothing
> 3.Try to shutdown or reboot
>
> Actual Results:
> The computer is not shutting down: "Reached target shutdown" and hangs
> there.
>
> Expected Results:
> Powering off the machine.
>
> For what it's worth, closing the lid won't suspend the system, but
> using the menu buttons for suspension will do it.
>
> To manage notifications about this bug go to:
> https:/
> 1594023/
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Aang (aang-aero) wrote : | #26 |
I have a Dell 14z-5423 - same issue on Ubuntu 14.04.5 and 16.04.1 :-(
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Blackbug (blackbug-nx) wrote : | #27 |
Okay, I got it fixed for now on my machine by reinstalling the current kernel. After this I can restart/shutdown without getting hung.
Not sure if this is the generic workaround.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
jtarin (jtarin) wrote : | #28 |
Works for me too with kernel upgrade
On Nov 3, 2016 1:40 PM, "Blackbug" <email address hidden> wrote:
> Okay, I got it fixed for now on my machine by reinstalling the current
> kernel. After this I can restart/shutdown without getting hung.
>
> Not sure if this is the generic workaround.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Poweroff or reboot hangs. Laptop won't shutdown. 16.04
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> This is about a fresh Ubuntu 16.04 install on a new laptop (asus
> x540sa). After pressing the shutdown button in the start menu; the
> shutdown procedure starts and in the final splash screen the system
> just hangs. Tried a second time by pressing Esc once the splash screen
> showed up and I saw that it reaches the line "Reached target shutdown"
> and just stops there, no matter how long I leave it there the machine
> won't turn off.
>
> I also tried a Kubuntu 16.04 fresh install on the same machine and it
> hanged too at the final splash screen where the pulsating logo
> stopped. Then I tried with Esc only to see the exact same line in the
> end.
>
> The issue seems to affect lately quite many users as shown by the
> google results of the past month / week or so.
>
> I have also tried shutting down from the console with shutdown -and
> all the parameters after that suggested online- and sudo poweroff but
> unfortunately they didn't do the trick. The exact same situation
> occurred.
>
> Unmounting the swap as suggested online doesn't work.
>
> Also rebooting the system is not working either due to the same issue.
>
> So right now the only way for me to poweroff the machine is to press
> the power button on the keyboard continuously.
>
> Reproducible: Always
>
> Steps to Reproduce:
> 1.Install OS
> 2.Do something, anything or nothing
> 3.Try to shutdown or reboot
>
> Actual Results:
> The computer is not shutting down: "Reached target shutdown" and hangs
> there.
>
> Expected Results:
> Powering off the machine.
>
> For what it's worth, closing the lid won't suspend the system, but
> using the menu buttons for suspension will do it.
>
> To manage notifications about this bug go to:
> https:/
> 1594023/
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Blackbug (blackbug-nx) wrote : | #29 |
I again have the same issue. Although not everytime. Its hard to reason why it hangs at times. If it happens frequently will reinstall the kernel once again.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniele Viganò (daniele-vigano) wrote : | #30 |
Could be related to this bug?
https:/
https:/
It affects kernels >= 4.8 on (as far as I know) any distro.
I'm experiencing problems on both Fedora 24 and Ubuntu 16.10 running kernel 4.8 on a Dell Latitude E5450 with a Samsung 850 SSD.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
VinDSL (perfect-pecker) wrote : | #31 |
@ Daniele Viganò (daniele-vigano)
We're both experiencing the same shutdown problems -- same OEM -- same kernels -- same Samsung 850 SSDs.
The only obvious difference is you have a Dell Latitude E5450 laptop, and I have a Dell Optiplex 7010 SFF desktop.
Since neither of us are experiencing shutdown problems with kernels <= 4.7, yes, I would judge that it relates to the bug(s) you listed above.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
b-ob (b-ob) wrote : | #32 |
Same problem with a fresh install of Lubuntu 16.10. No problem at all with Lubuntu 16.04. I've tried a live Kubuntu 16.10: same problem. It seems to be a bug related to kernel 4.8, since live Fedora 24 (kernel 4.7) is fine but live beta Fedora 25 (kernel 4.8) doesn't shut down.
It seems that the computer (Dell Optiplex 9010 with SSD) is trying to access the disk after the line "Reached target shutdown", since it gives some errors like "ata1.00: exception Emask...", "ata1.00: failed command..." and the like. After a while, it prints "ata1: reset failed, giving up" and finally a "reboot: Power down" and then turn the power off (5 to 10 minutes after having printed the line "Reached target shutdown").
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniele Viganò (daniele-vigano) wrote : | #33 |
So, it seems we are all on Dell with a Samsung SSD 850 drive. Next week I'll have a chance to try a different SSD from Kingston. I'll see if the bug is still reproducible.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Blackbug (blackbug-nx) wrote : | #34 |
I have HP envy ultrabook. However, I do have samsung 850 SSD..so i guess it all comes to SSD then
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
VinDSL (perfect-pecker) wrote : | #35 |
My biggest fear is that during one of these 'freezing' episodes my Samsung 850 SSD will remount the root partition as read-only. I've had several HDDs go read-only, over the years, and it's a PITA to recover from it, especially in RAID configs.
Somebody will to need to handle this situation upstream. Two likely scenarios would be either a Linux kernel patch, and/or a firmware upgrade from Samsung. In the meantime, we're all sitting on ticking time bombs.
I suppose it goes without saying, but make sure you're fully backed-up !!!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Daniele Viganò (daniele-vigano) wrote : | #36 |
It seems that the code causing the bug will be reverted in 4.9-rc7: https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
EWoldhek (3y9-elis-fkz) wrote : | #37 |
Same here on Samsung Ultrabook core i5 after upgrading to 16.10.
Linux version 4.8.0-27-generic (buildd@lgw01-11) (gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) ) #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC 2016
SSD: Samsung MZNTE128
After "Reached target Shutdown" i get:
- ata1.00: exeption Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
- ata1.00: failed command: Flush CACHE
Some other lines with - ata1: comreset failed
Hope you guys can find it.....
Regards, Erik
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
VinDSL (perfect-pecker) wrote : | #38 |
Kernel 4.9-rc7 fixed it !!!
I waited until the Ubu Mainline kernel was available, just to make sure.
LINK: http://
@Daniele Viganò, thanks for all the effort(s) you went to, over in the mailing lists and bugzilla, to make this happen.
Good job !
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Davidiam (hectorjerezano) wrote : | #39 |
I can confirm On my dell laptop E7450 With kernel 4.8 BUG reported here. With 4.9 rc7 this BUG is FIX!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
EWoldhek (3y9-elis-fkz) wrote : | #40 |
Will it be fixed in 4.8 through standard udpates?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Blackbug (blackbug-nx) wrote : | #41 |
I have installed the 4.9-rc7
kk@blackbug:~$ uname -r
4.9.0-040900rc7
However, laptop still hangs on shutdown. At times the shutdown is proper and within seconds. However, most of the time it takes more than 5mins to shutdown or it just hangs.
Does anyone else have the same issue?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Renê Barbosa (renebarbosa) wrote : | #42 |
@Blackbug Yeah, same thing here. I'm using the same kernel version on a Dell Inspiron 5447.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
humblyonhisground (lazarev-z) wrote : | #43 |
Installing kernel 4.9 as per http://
fixed the shutdown/restart problem for me on Kubuntu 16.04.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Thinkren (thinkren) wrote : | #44 |
Has it been confirmed that only Samsung SSD are affected? I'm experiencing the same problem on a Gigabyte Brix (GB-BXBT-1900) running on a Toshiba OCZ TR150 (120gb). Just installed Lubuntu 16.04 LTS and stumbled on this bug.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Thinkren (thinkren) wrote : | #45 |
Never mind. Despite the dirty shutdown, a subsequent post-installation update resolved the problem.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Renê Barbosa (renebarbosa) wrote : | #46 |
This is definitely NOT a kernel problem.
I was using the kernel 4.4 of Ubuntu 16.04 in the same machine running Ubuntu 14.04 and this problem never happened.
My machine specs:
Dell Inspiron 5447
Core i5-4210U
8 GB RAM
SSD 480 GB SanDisk
Intel/Radeon R7 M265 Hybrid Graphics
In 16.04, these hangs during shutdown occurred in the following kernels:
4.4 (Default)
4.8 (HWE-Edge from repositories)
4.9 (Mainline)
This is not a systemd problem?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
ezfox (ezfox) wrote : | #47 |
Same here, Alienware M11xR1 Laptop running Xubuntu 16.10 on a OCZ Vertex SSD.
Tried all thing suggested above but nothing helped.
When booting live Xubuntu from stick, reboot and shutdown are working fine.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jill Murray (jillmurray) wrote : | #48 |
I am having the same problem, with cinnamon 18 3.0.7 the Acer laptop F54os freezes on the logo when shutting down. It shuts down correctly when I open a terminal and use sudo poweroff
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Reinhard Zierke (reinhardzierke) wrote : | #49 |
My Dell Optiplex 7040 with SSD worked fine with the 4.8 kernel. But after upgrading its firmware from 1.4.5 to either 1.5.4 or 1.5.7 I had the DRDY error at shutdown too. Kernels 4.4 and 4.9 shut down cleanly. Afer downgrading the firmware back to 1.4.5 kernel 4.8 shuts down cleanly again.
A similar problem is with our Optiplex 9020s (with hard disks). In the pool room that I upgraded to firmware A17 recently, kernel 4.8 shuts down with the DRDY error. Kernel 4.4 shuts down fine. In the pool room with the 9020s that have older firmware A07 or A12, kernel 4.8 shuts down fine too.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ruslan Gol (russgolubchik) wrote : | #50 |
Same issue with my Dell E5450. Created bug report:
https:/
No resolution yet. Please fix!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ruslan Gol (russgolubchik) wrote : | #51 |
Same issue with my Dell E5450, Crucial MX100 SSD running Ubuntu 16.10, 4.8 Kernel,. Laptop shuts down instead of reboot.
Created bug report:
https:/
No resolution yet. Please fix!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ruslan Gol (russgolubchik) wrote : | #52 |
Just fixed it by following this:
http://
My OS 64bit, download kernel accordingly:
1. cd /tmp/
2. wget http://
3. sudo dpkg -i *.deb
4. reboot
uname -a
Linux ruslan 4.9.0-040900-
Thanks!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Axel Schmidt (arties) wrote : | #53 |
Thanks to Ruslan Gol, this worked for me too!
I have a lenovo thinkpad p51s with a SAMSUNG MZVLW512HMJP-000L7 512gb ssd and kubuntu 16.10.
After update the kernel to 4.9.0-040900-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jelle De Loecker (skerit) wrote : | #54 |
I have a Dell XPS 13 developer edition, I upgraded to Ubuntu 17.04 and it still doesn't shutdown properly.
By the way: 6 shutdown jobs (5 that are for unmounting the encrypted home folder and 1 for my NFS mount) time out before the "shutdown target" is reached.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jelle De Loecker (skerit) wrote : | #55 |
Follow up to my post 54: I applied the fix posted in bug #1577120 and now unmounting the NFS drive works, and the system shuts down just fine.
So I would guess the real underlying issue many people here have is that, even though systemd is terminating timed out jobs it doesn't actually shut down the system.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ed Huyer (arcanum3000) wrote : | #56 |
Any word on this getting fixed? I'm seeing it on freshly installed 16.04.2 servers running kernel 4.4.0-83. They hit "Reached target Shutdown" and just sit there when I reboot them. I've tried forcing acpi, as well as tweaking various BIOS options and reducing the job timeout settings for systemd.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Yovan (navoytak) wrote : | #57 |
please refer to my problem in the following thread:
https:/
I note that System D (aka system 500) is a bit new. I am one of the casualty trying to transit into this new system.
Luckily for me, i manage to clear the problematic symptoms of not shutting down by removing a Sysvinit service using rc-local.service which i created myself.
I hope i can point someone in the right direction. Happy problem solving.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Cedric Bhihe (cedric-bhihe) wrote : | #58 |
Same issue on fresh UEFI/GPT install of Zesty (ubuntu 17.04 with Gnome Desktop) on a brand new Dell XPS 15 9560.
Editing /etc/default/grub with:
GRUB_CMDLINE_
seems to solve (or supress ?) the pbm.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Hey! (press-1p-start) wrote : | #59 |
I have the same problem on a Toshiba a210.
I was trying to install Elementary OS Loki when i found out.
Elementary Loki (16.04) with kernel 4.10 - Reboot and Shutdown doesn't work.
Elementary Loki (16.04) with kernel 4.4 - Shutdown works, but reboot makes the Bios screen (toshiba logo) freeze.
Ubuntu 16.04 liveusb with 4.4 have the same problem as Loki 4.4.
If you press quickly the f2 button, after some time you see the hard disk led light up and the computer enters the boot screen, but when you try ctrl+alt+del it goes back to the freeze. Only the power button makes the problem go away.
" https:/
Does anybody knows what could be causing the Bios screen freeze?
Thanks.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Hey! (press-1p-start) wrote : | #60 |
I have some more things to add.
On 4.10, if you reboot or shut down as soon as you can, it works, but it continues to make the bios screen freeze.
I don't know if is 16.04 or a >4.4 kernel that is causing this, but it's still present on 4.10.
When the computer reboots, i see this two failed lines before the computer reboots:
[ Failed ] failed unmounting /rofs
[ Failed ] failed unmouting /cdrom.mount.
Then the computer reboots and the bios freezes.
If i press the F12 (boot device selector) and wait some time, i can choose the liveusb, but the os gets stuck on the spash screen and i can see this message:
ata1: softreset failed (device not ...)
No medium found can't open /dev/sr0:
No medium found can't open /dev/sr0:
No medium found can't open /dev/sr0:
No medium found can't open /dev/sr0:
No medium found can't open /dev/sr0:
I'm testing this on a live usb btw.
Any idea?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
giovano iannotti (iannotti) wrote : | #61 |
I have the same issue, fresh 17.10 install, Asus x756U, Intel® HD Graphics 620 (Kaby Lake GT2), Intel® Core™ i7-7500U CPU @ 2.70GHz × 4. I have tried proprietary nVidia driver and xorg. It's the same thing. I also have a wifi dropping issue.
Editing GRUB didn't make any difference.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Noor Jahesh (noorjahesh) wrote : | #62 |
I had the same issue after installing fresh Ubunut 17.04 on laptop Dell Inspiron, after installing kernel 4.9 ,the issue has been solved.
http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
wimduk (wim-dukker) wrote : | #63 |
I got the same problem on a Lonovo ideapad 100.
Installed via standard update manager kernel 4.4.x and the problem was solved.
Regards, wimduk
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Pablo Fontoura (pablofontoura) wrote : | #64 |
I got the same problem, but if disable splash on /etc/default/grub the problem are solved.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Samir Tuffi Saliba Junior (samirslb) wrote : | #65 |
I had Ubuntu 16.04 and Windows 10 dual-boot and experienced this bug.
Formatted my DELL-Vostro14, installed Mint and I'm experiencing this once again.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Peshmerge (peshmerge) wrote : | #66 |
I have bought a new Asus Vivo Book pro, and I have the same problem.
In the beginning I couldn't install Ubuntu 16.04 at all. I could do that by changing acpi=off in the grub file to get over the problem. The installation was always stuck at "Preparation for install".
Now after installing the Ubunut 16.04 it takes more than a minute to reboot of shutdown ! I hope this will be fixed soon!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
JohnDoe_71Rus (johndoe99) wrote : | #67 |
this is a problem with the kernel. Starting with some version. I installed Lubuntu 18.04 on the usb hdd and checked on the 2 systems. On the desktop intel turns off and reboots without problems.
On the laptop dell inspiron 1501 there are problems with the reboot and shutdown. The power does not turn off. But entering hibernate mode turns off the power normally.
Checked calculate linux 17.12.2 behavior on the laptop is the same, does not power-off and reboot
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
JohnDoe_71Rus (johndoe99) wrote : | #68 |
GRUB_CMDLINE_
don't help me
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Konstantin (hi-angel-y) wrote : | #69 |
@JohnDoe_71Rus are you running a kernel 4.9 or higher? Per discussion above, 4.9 seems to have solved the problem for many peoples.
I wonder if the problem is resolved for OP, and, if somebody still affected, it should be opened as a separate bug.
Changed in linux (Ubuntu): | |
assignee: | damiano (damiano1996) → nobody |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
JohnDoe_71Rus (johndoe99) wrote : | #70 |
@Constantine
lubuntu 14.04.5 LTS with kernel: Linux x86 64-bit version 4.15.5-
from kernel.
Lubuntu 18.04 and calculate linux 17.12.2 kernel of the box x86 version
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
ClickyClack (clickyclack) wrote : | #71 |
This bug exists with no workaround on the following Lubuntu installation:
Version: Ubuntu 16.04.5 LTS
Kernel: 4.15.0-29-generic
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
ClickyClack (clickyclack) wrote : | #72 |
I should also mention that I'm using a Samsung 850 SSD. I'm new to debugging linux so let me know if there's any more useful information I can provide.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Julian (julianwhettam) wrote : | #73 |
Same problem.
Version: Lubuntu 18.04.01
Kernel: 4.15.0.33-generic
Dell Vostro 1000, AMD Athlon 64 x2 Dual core TK-55
Kingston SSD
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Aravind (aravindr) wrote : | #74 |
Have the same issue on Xubuntu 18.04 on an intel J1900 machine with Kingston SSD. We also have a similar machine with exactly the same equipment but not having the Kingston SSDd running with no issues at all, looks like the Kingston SSD seems to be causing some problem. Hope ubuntu help us fix this issue.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Aravind (aravindr) wrote : | #75 |
Bug exists in 4.9 kernel too. I have opened a bug for this.
https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Sergey Zolotarev (szx) wrote : | #76 |
I have this problem in 18.10, in 18.04 shutdown/restart worked fine
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Hey! (press-1p-start) wrote : | #77 |
Hi.
Same problem on a Toshiba A210. AMD processor and AMD graphics.
This issue started after kernel 4.4.
Ubuntu 16.04 with 4.4 - Works.
Ubuntu 16.04 with 4.15 - Shutdown and reboot doesn't work.
Ubuntu 18.04 with 4.15 - Shutdown and reboot doesn't work.
This leads me to believe that is a kernel problem.
The weirdest part is that if you try to reboot or shut down as fast as you can after login, everything works like it should.
I have three computers using Ubuntu, but only one is affected by this issue.
Thanks.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Kai-Heng Feng (kaihengfeng) wrote : | #78 |
Hey,
Please file a new bug for your issue, thanks!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Kai-Heng Feng (kaihengfeng) wrote : | #79 |
I thinks it's LP: #1776616 for your issue.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Hey! (press-1p-start) wrote : | #80 |
Hi.
On my computer the transition from 4.5.7 to 4.6.0 is the cause of this bug.
Can anyone try to install the following kernels to see if this bug happens?
http://
http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dave (dbakerp) wrote : | #81 |
Same bug appears on my Lenovo M58p desktop with Ubuntu 16.04.5 LTS kernel 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Liomar (liomarhora) wrote : | #82 |
I was having the same problem on Debian 9, but my PC was old.
When I looked at linux-image and linux-header in synaptic, there were installations for old PCs and modern PCs, on my old PC was installed the version for modern Pcs. I installed the correct version and uninstalled the wrong one. Worked perfectly.
Ex:
linux-image-
linux-image-686 - Linux for older PCs (meta-package)
linux-image-
linux-image-686-pae - Linux for modern PCs (meta-package)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Manan Solanki (manan2110) wrote : | #83 |
The same issue is also reproducible for me on my HP Pavilion N004tx laptop. I'm using Ubuntu 18.10.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vishal Dindalkop (vishald) wrote : | #84 |
I had similar issues when i installed Ubuntu i tried to boot ubuntu but it got hang because of ACPI error
i made acpi off so it can boot in but when i tried to shut down it got hand this time
Reason is simple
Its related to your graphic card
step 1:
i went through these proceess
->booted into system with acpi off from grub command
since i was not able to without doing so
step 2:
later when i got into ubuntu
i did
(this step neccessary or not i'm not sure, included it since i had followed it) i think its very necessary
->sudo apt-get update
->sudo apt-get upgrade
step 3:
Install graphic card Driver
https:/
after doing this once you might hang but on restart you wont need acpi off
you can run ubntu without any hang during start splash screen or shutdown splash screen
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
JohnDoe_71Rus (johndoe99) wrote : | #85 |
option PowerNow Disabled in BIOS looks like fix the problem. But the CPU temp is grow up. And it work many years before with PowerNow Enable without problem.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Dariusz Deoniziak (darekdeoniziak) wrote : | #86 |
I do have the same problem since Ubuntu 17.14, it doesn't matter if it is Ubuntu distribution or any of its flavours (e.g. Kubuntu which I am using currently). I do not remember if it worked fine on 16.04, all I can tell I was always doing distro upgrade and haven't installed fresh Ubuntu installation since 16.04.
Laptop is Dell Inspiron 7548.
There are various blog or forum posts about this issue, mostly suggesting to edit grub (some about editing defaulTimeout in system.conf), unfortunatelly editing acpi settings or editing anything similar doesn't work.
I do not use any custom ppa other than google/chrome. Means I am using stock/distro mesa drivers too.
The laptop freezes on splash logo only during shutdown (reboot works fine). I have noticed that laptop freezes on poweroff command (visible on nosplash). The laptop sometimes doesn't freeze when battery is not fully charged, the less battery is charged the lesser chances that laptop will freeze. On 15-30% of battery laptop does shutdown fine, never noticed freeze. But when battery is 90% or fully charged, or charging, the freeze almost always happens.
This laptop does have battery test in UEFI, test says battery is in fine condition. Anybody else noticed any connection with shutdown freezes and battery?
One more thing worth noting, once following some another forum posts I have edited reboot command behaviour to shutdown laptop, laptop did shutdown always after invoking reboot, even when battery was fully charged and charging. But I have reverted this change because I need reboot more than shutdown.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Keith (kballthingsliunx) wrote : | #87 |
Sounds like broken record here, oh no broken shutdown here actually.
Bodhi Linux 4.2 on old hardare Aspire 5000 laptop, was wooring fine till a day or two ago.
Hangs at shutting down several things says all stopped down to hardware clock something or another.
can hit Esc a couple times and it progresses but still just stops.
Will boot fine with a Power Button Hold down and restart.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
hardyn (arlenn) wrote : | #88 |
Had same issue with MSI GP73 laptop. Problem was solved by installing the NVidia "blob" drivers.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Slawomir (slaw001) wrote : | #89 |
Hi, I have a DELL Latitude E5520 (4.15.0-52-generic #56~16.04.1-Ubuntu)
Problem was solved:
/etc/default/grub
changed the entry bellow:
GRUB_CMDLINE_
on the following:
GRUB_CMDLINE_
and
sudo update-grub
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Max Argus (argus-max) wrote : | #90 |
Same Problem Dell XPS 15z
Kernel: 4.18.0-22-generic
OS: 18.04.02
Window manager: KDE
Not using Nvidia blob drivers.
Editing grub with "acpi=force reboot=pci" didn't help.
Sometimes also partially freezes when using firefox (mouse dosen't move, ping command dosen't work, can't kill -9 firefox process)
tags: | added: cscc |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
B. C. Schmerker (bcschmerker) wrote : | #91 |
This hang on shutdown and/or reboot is NOT confined to portables. I encountered the issue installing xubuntu™ 18.04-LTS on an emachines®/acer® EL1210-09 (2.3 GHz Advanced Micro Devices® Athlon® LE-1620; nVIDIA® nFORCE® 720 chipset; 2 x 2 GiB DDR2 main memory) with a Shuttle® PSU upgrade (PC6300001 in for stock 220W LITEON®) and the planar C77 geForce® 64-bit GPU by-passed for the nVIDIA® GF-109 on an msi® N610GT-MD1GD3/LP half-height video display adapter. I normally use:
GRUB_CMDLINE_
in /etc/default/grub, which is how I confirmed the issue: Depending on shutdown or reboot option, the system halts at "Starting reboot..." or "Starting power-off...", forcing a manual power-down. Will report back after testing:
GRUB_CMDLINE_
and:
GRUB_CMDLINE_
I'd rather save the C77 geForce® driver set (provided to Canonical Ltd. by nVidia Corporation) for the nFORCE® 720 as a last resort, as it affects Kernel behavior in both startup and shutdown.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
B. C. Schmerker (bcschmerker) wrote : | #92 |
Update: acpi=off only got me to a timestamped kernel message "reboot:System halted". acpi=force had no effect. Repeating report to Bug 1776616, which is specifically relevant to Kernel 4.15-n-generic on xubuntu™ 18.04-LTS.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
B. C. Schmerker (bcschmerker) wrote : | #93 |
Update: Issue worked around with nVIDIA® geForce® driver 340.107 for C77 GPU in MCP78 northbridge (package:
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Tushar (tushar321) wrote : | #94 |
This issue still persists.Mine is an
Hp laptop with an Intel Bay Trail processor, Intel HD graphics(Not Nvidia), 8GB RAM with Dual boot Windows and Ubuntu 16.04.2. Bios version F.46 and kernel version 4.15.0-55-generic
Whenever I try to SHUTDOWN/
I tried to Re-install ubuntu with 16.04.6 while installing it displayed error related to APCI. somehow it got installed and when I checked dmesg it showed this error message
"ACPI Error: [\_PR_.CPU0._PPC] Namespace lookup failure, AE_NOT_FOUND (20170831/
"ACPI Error: Method parse/execution failed \_SB.PCI0.
I tried almost everything I found on internet acpi=force, acpi=off and other stuff. It's discouraging from 2016 to 2019 there is still no permanent fix for this issue. some people on internet tried some or other fix for some it worked for some it didn't. Did anyone one of you found the fix for this ?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
JohnDoe_71Rus (johndoe99) wrote : | #95 |
try 5.2.8 from https:/
the same, last mesage in console
Started Show Plymouth Power Off Screen
Starting Power-Off
[... ] systemd-shutdown [1]: Failed to wait for process: Protocol error
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Vadym Stupakov (red-eyed) wrote : | #96 |
I have same problem and solved it.
workaround is: https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Guy Mandor (guy-mandor) wrote : | #97 |
@VadymStupakov: You're a saviour. I had been struggling with this issue for over a year. The solution worked perfectly. My power button Thanks you!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ashwin Biju (regenhalogen) wrote : | #99 |
I had the same problem with elementary os i fixed it by disabling the usb 3.0 option in the bios of my hp laptop....
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Marko T (tolima1) wrote : | #100 |
Hi, I have the same problem with not being able to reboot or shutdown.
Error is displayed: "Failed to power off system via logind: There's already a shutdown or sleep operation in progress"
Ubuntu 20.04 on Dell Pavilion M6600.
I tried modifying the "quiet splash acpi=force" but without success.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Launchpad Janitor (janitor) wrote : | #101 |
Status changed to 'Confirmed' because the bug affects multiple users.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
tyler krueger (pumking10) wrote : | #102 |
its effecting ubuntu 20.04 if there is a way to fix it please help me out.
Changed in ubuntu: | |
status: | New → Confirmed |
affects: | linux → ubuntu |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
VinDSL (perfect-pecker) wrote : | #103 |
Every machine is different. Here's the grub that I use on 'doorstop' machines:
# If you change this file, run 'update-grub' afterwards to update
GRUB_DEFAULT="0"
GRUB_TIMEOUT_
GRUB_TIMEOUT="10"
GRUB_DISTRIBUTO
GRUB_CMDLINE_
GRUB_CMDLINE_
GRUB_GFXMODE=
It knocks a few seconds off of boot times, and shuts them down in a heartbeat.
Here's the 'systemd-analyze time' result on my Dell Dimension 3000 box, circa 2004:
Startup finished in 3.650s (kernel) + 7.044s (userspace) = 10.694s
graphical.target reached after 7.008s in userspace
No joke...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
atefrihane (atfinho) wrote : | #104 |
I'm using dell 3543 and ubuntu 20.04
reboot but works but power off hangs
is there a way to fix it please ??
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Launchpad Janitor (janitor) wrote : | #105 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in ubuntu: | |
status: | New → Confirmed |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Stefano (cmarlowe) wrote : | #106 |
I have the same issue, I'm using an ASUS k50in with graphic card Nvidea GT220M.
When I power off my laptop the procedure stops at the output line Reached target Power-Off.
This is the output of the command uname -a for my laptop
Linux stefano-K61IC 5.8.0-40-generic #45~20.04.1-Ubuntu SMP Fri Jan 15 11:35:04 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
I have tried in the grub configurations the GRUB_CMDLINE_
Can you suggest a way to fix it? Or some debug steps that can be performed to better understand the issue?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jan Johansson (insomniacno1) wrote : | #107 |
Lenovo Thinkpad X300, 4GB Ram, INTEL SSDSA1MH160G1HP (045C8781)160GB SSD, Intel GMA X3100 i915, battery SANYO 42T4522 77% capacity though charges to 100%.
Peach OSI TW 16.04 LTS build on Xubuntu, Kernel 4.4.0-217-generic.
Problem with shutdown started with 4.4.0-216-generic and is still in 4.4.0-217-generic which is the newest kernel for my setup.
If the machine has been idle for a while, sometimes with Firefox 88.0 open, sometimes after using VLC player - then it hangs on shutdown, Screen is off but wifi and bluetooth light is on(its off when totally shutdown). At this point not even ESC work(as the screen is off and never comes on), only by holding the power button the laptop turns off.
Restarting sometimes work ok, but from time to time it can take up to 10 min to start up(where normal startup is 30seconds).
Editing grub and adding noefi after quiet splash, worked for a while and then last night it would not shut down again and I had to use power button. this morning it started up normal 30seconds.
I have had updates comming in, I have installed Intel graphic tool to update the driver but problem persist, so don't think its a graphic card driver issue.
Many here has reported it on other systems with totally different config, so I think this is a kernel issue that seem to pass through in newer kernel updates.
Also seem that it is not only 16.04 since it has been reported in newer versions too.
I'm still using 16.04 because there is no 20.04 Peach(now named Patriot) after the author died in september this year - I might move to 20.04 or newer when most of the bugs has been addressed.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jan Johansson (insomniacno1) wrote : | #108 |
So removing quiet splash and adding noefi to grub and editing
sudo xdg-open /etc/systemd/
removing the # infront of #DefaultTimeout
Seem to have fixed my issue
I found the last bit here:
https:/
Please comment and let me know if it solves it for you too.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jan Johansson (insomniacno1) wrote : | #110 |
I have changed DefaultTimeoutS
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jan Johansson (insomniacno1) wrote : | #111 |
I had the issue again. so my previous change didn't work.
I have changed DefaultTimeoutS
I tried turning off wifi byt rfkill block all from terminal prior to shutdown, that just ended up in black screen as usual but this time wifi was off, but laptop still on.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jan Johansson (insomniacno1) wrote : | #112 |
I have investigated further, it would seem that it is the shutdown function in ubuntu and flavors that is the problem, because sudo poweroff in terminal work just fine.
I suggest the ones still affected by this bug, try to open terminal and type:
sudo poweroff
your password
Just to see if it work for you, please let me know.
Could one of the experts here come up with a script that do the poweroff function without having to type password?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jan Johansson (insomniacno1) wrote : | #113 |
So sudo poweroff seems to fix the problem, somehow, because if I do that and then next time shutdown normally then the laptop shuts all the way down - meaning turn off.
Weird.
So sudo poweroff it is, should be put instead of shutdown, because it would seem that one is faulty, and in my case with 16.04 most likely is not getting solved.
for 18.04 and later there might be some solution.
I still call out for a script as temporary solution!
Thank you in advance
Jan
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jan Johansson (insomniacno1) wrote : | #114 |
Hi again, so since october 28, I have been trying to install and run an old kernel from before this shutdown problem happened and I am now running 4.4.0-210-generic, for the last week(and I use my laptop every day most of the day), I have had no shutdown problems.
Since this problem occur in newer kernels too, than maybe developers can look to this kernel and see what is different, that might cause the problem.
To people who want to use this older kernel, just open synaptics and look first to what you have installed by searching for your kernel version number - do not add linux-image or linux-headers.
You should see what is installed and modules. Make a screenshot or write it down, then look for this old kernel the same way and install the items from your list.
Wait for it to finish.
Then either use Grub customizerI use this as there is a GUI and a lot of options, like having a list of kernels shown on start up) or you can just run
sudo update-grub
from terminal
Restart your machine
Edit these instructions to fit your own system, that might be different from mine.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jan Johansson (insomniacno1) wrote : | #115 |
I switched to Linux Mint 20.2 Uma Cinnamon and now I don't have shutdown problem anymore.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
ranjit (ranjit3434) wrote : | #116 |
I had dual OS installed on my old lenovo laptop
windows 7 & bodhi linux. but my linux system stuck at shutdown screen. i found a solution which worked for me,
#GRUB_CMDLINE_
then grub update using
#sudo update-grub
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Jan Johansson (insomniacno1) wrote : | #118 |
Just to add to this, it is definitely a kernel problem, and since it comes back once in a while it would suggest that its the same programmer/
I am on Linux mint 20.2
Kernel 5.4.0-162-generic
Status changed to 'Confirmed' because the bug affects multiple users.