Created attachment 1475712 [details] Picture of where system stops reboot. Never proceeds past this point. Description of problem: System (2016 Dell XPS) will not shut down or restart. Hangs on error waiting for firewalld daemon. Then moves to Stopping Monitoring of LVME mirrors. System will not proceed past this point. See screenshots Version-Release number of selected component (if applicable): Unknown - Fedora 28 Gnome How reproducible: Attempt to restart system Steps to Reproduce: 1. Click Power 2. Choose Restart or Reboot 3. Firewalld times out after 3 minutes then proceeds to LVME mirror error and never reboots. Hard reset. Actual results: System does not reboot, have to push power button to shut down. Expected results: System reboots or shuts down. Additional info: System is 2016 Dell XPS 13" Fedora 28 Gnome No issue with Mint Cinnamon only happening with Fedora 28. All other services seem to work fine including boot. Only hangs on restart or shutdown. Noticed issue does not happen as often when manually choose Kernel 4.16. Happens everytime on 4.17
I've had a failure to power off since about F26 through F28. I just upgraded from Fedora 28 to Fedora 29. The problem still exists for me. I had no problems until these later releases. I am using SELinux, LVM partitioning, and KDE. The system seems to go thru the shutdown process fine, but finally stops both drives, but does not turn off power. This happens on shutdown or reboot. I have tried all options of poweroff, shutdown, reboot, etc. commands with the same results. It doesn't matter whether I try to shutdown from KDE (xterm window or UI), or after logging out from KDE and <Alt Fn> to a console. So, the only way to power off is at the power supply or holding down the power button. I can supply more info if needed, if given instructions on what/how.
(In reply to David Allen from comment #1) > I've had a failure to power off since about F26 through F28. I just upgraded > from Fedora 28 to Fedora 29. The problem still exists for me. I had no > problems until these later releases. > > I am using SELinux, LVM partitioning, and KDE. The system seems to go thru > the shutdown process fine, but finally stops both drives, but does not turn > off power. This happens on shutdown or reboot. I have tried all options of > poweroff, shutdown, reboot, etc. commands with the same results. It doesn't > matter whether I try to shutdown from KDE (xterm window or UI), or after > logging out from KDE and <Alt Fn> to a console. > > So, the only way to power off is at the power supply or holding down the > power button. > > I can supply more info if needed, if given instructions on what/how. The last lines shown in the console: kvm: exiting hardware virtualization synchronizing [sdb] scsi cache synchronizing [sda] scsi cache After which system just sits. No power off.
This problem was solved on Fedora 29 after installing Nvidia's driver. I also noticed that it went away with another Nvidia video card using the Nouveau driver. However, with my current video card (GeForce 780 ti) and using the Nouveau driver, the system will not power off. Switching to Nvidia's driver fixes that. So, apparently the problem for me is video driver-related.
After a kernel update, the problem is back. But now the system wants to go into an S5 suspend state. How do I disable this?
Same sympton here, but AMD integrated GPU. Was fine on 26, I went to 29 release-by-release with fedup and now it hangs after "sudo reboot". All lights are on the front as if it's running, but there's no answer over the network. I have to press the power button to switch off, then again to boot. This machine is headless. $ sudo journalctl -b -1 -n -- Logs begin at Mon 2015-08-10 16:08:50 BST, end at Wed 2019-02-20 22:12:04 GMT. -- Feb 20 19:49:28 bookcase systemd[1]: Reached target Shutdown. Feb 20 19:49:28 bookcase systemd[1]: Reached target Final Step. Feb 20 19:49:28 bookcase systemd[1]: Starting Reboot... Feb 20 19:49:28 bookcase systemd[1]: Shutting down. Feb 20 19:49:28 bookcase lvm[25417]: /run/lvm/lvmetad.socket: connect failed: Connection refused Feb 20 19:49:28 bookcase lvm[25417]: WARNING: Failed to connect to lvmetad. Falling back to device scanning. Feb 20 19:49:28 bookcase kernel: printk: systemd-shutdow: 42 output lines suppressed due to ratelimiting Feb 20 19:49:28 bookcase systemd-shutdown[1]: Syncing filesystems and block devices. Feb 20 19:49:29 bookcase systemd-shutdown[1]: Sending SIGTERM to remaining processes... Feb 20 19:49:29 bookcase systemd-journald[443]: Journal stopped I have no idea why lines from lvm are there. I don't use it.
upstream bug report with shutdown logs : https://github.com/systemd/systemd/issues/11886
Upstream says this is Dracut e.g. Fedora's fault.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
WFM now in Fedora 30
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.