Fedora 24 hangs on restart after an update a few days ago. How do I fix this?

asked 2016-11-26 16:12:55 -0500

Mechanizoid gravatar image

updated 2016-11-26 22:49:48 -0500

Recently I and my family got three matching Lenovo Thinkpad 11e's (the ones with an Intel N2940 processor, a 500 gb hdd, and Win7 pro preinstalled), wiped Windows, and installed Fedora 24 on all three. Right out of the gate, everything worked--volume buttons, brightness buttons, wifi, webcam, everything, pretty good experience. :)

However, after an update a few days ago, the restart button accessed through the power button in the upper right menu in Gnome doesn't restart the laptop. It just hangs at the black screen, with the hardware still running, after Fedora shuts down. I have to hold down the power button for several seconds to shut down the computer. After forcing it to shut down, I can restart and Fedora reboots without issue. Fedora will power off without a problem, it's only restart that hangs.

I know that restart worked before, because I restarted after the first big round of updates. At first I thought it might just be my machine, but we tested restart on my father's laptop and his does the same thing. We know that his laptop restarted correctly before, because we restarted it after the first big round of updates as well. So I suspect it was related to a later update. Unfortunately, I don't remember the exact name of the update just before this issue, only that it was lib-something-or-other and that Software gave a notification of it. I used dnf upgrade, my father probably updated during shutdown without realizing it.

I'd like to fix this, since it's annoying. Also, I want to upgrade to Fedora 25 through the package manager (especially if it might fix this!) but I'm a little worried that this restart issue might hang up the process. I'm new to both Fedora and linux in general, so any advice will be greatly appreciated!

Edit: Since fcomida told me how to access dnf logs, I was able to get some info on the update I installed just before first noticed this issue. After running dnf history info on the transaction in question, I got this:

Transaction ID : 5
Begin time     : Mon Nov 21 14:58:45 2016
Begin rpmdb    : 1500:02f5366807919fb554aeeef9d0a354519444afbe
End time       :            14:58:47 2016 (2 seconds)
End rpmdb      : 1500:cb6b3d44619a148e370e3aef6e6992e2650fdc90
User           : ********
Return-Code    : Success
Command Line   : upgrade
Transaction performed with:
    Installed     dnf-1.1.10-1.fc24.noarch        @updates
    Upgraded      rpm-4.13.0-0.rc1.27.fc24.x86_64 @koji-override-0
Packages Altered:
    Upgraded libsndfile-1.0.25-20.fc24.x86_64 @koji-override-0
    Upgrade             1.0.27-1.fc24.x86_64  @updates

So it looks like the update was libsndfile-1.0.25-20.fc24.x86-64, unless it was just a coincidence.

edit retag flag offensive close merge delete



dnf history and dnf history info <transaction>, journalctl for looking at the logs

fcomida gravatar imagefcomida ( 2016-11-26 20:34:25 -0500 )edit

Thanks for the tip, now I can see the update I installed just before this issue for occurred, maybe that will help resolve it! :)

Mechanizoid gravatar imageMechanizoid ( 2016-11-26 22:40:43 -0500 )edit