Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

13
  • 1
    Assuming that this happens on Linux, you can try pressing F12 just after shutdown procedure starts. This will give you a verbose output on what's happening in the background. Commented Jan 5, 2017 at 15:43
  • @MayankVerma I did, and the last thing it says is something like "Exception:Emask" but it is only there for half a second so I cannot read the rest Commented Jan 5, 2017 at 15:47
  • And also something about bluetooth firmware that could not be loaded, but that shouldn't cause the shutdown process to crash, should it. Why is it loading firmware at shutdown anyways Commented Jan 5, 2017 at 15:54
  • Can you post your errors from journalctl -p err ? Commented Jan 7, 2017 at 22:44
  • I can. The problem is, that my journalctl does not output everything due to ratelimiting, and the options "RateLimitIntervalSec" and "RateLimitBurst" seem to be ignored... Commented Jan 7, 2017 at 22:48