I have a Librem 13 v2. Often, after shutting down, the computer hangs at the PureOS logo. I’ve tried leaving it for a few minutes, but the computer is still hanging. I have to hold the power button down for about 10 seconds to power off.
This doesn’t happen all the time, but often enough to make things a little frustrating. This is a fresh install of PureOS, and the problem disappeared for a while after I did a firmware update about two weeks ago. However, it’s come back.
Has anyone else experienced this? If so, is there a solution?
Usually it is just a stop job waiting to be completed. Similar to processes that don’t want to close down when you shut down windows. Usually these processes are given a window of time to complete, before they are closed, to help prevent data loss.
You may just see the Purism logo but there are jobs waiting to be closed in the back ground. Next time you have this problem, wait for about 5 minutes and see if the computer goes off by itself.
It is also helpful that you close all applications before shutting down or restarting as this should help minimize the occurrence of this happening.
If there’s a process that is wedged then you will need to wait 5 minutes or so before further messages appear, and the messages will tell you that a process is wedged and its process id, which, with preparation prior to shutdown, would tell you which process this is.
If no process is wedged then I would guess there’s some firmware / software problem where it gets to the final step of wanting to power off but it fails to communicate this correctly to the hardware so it never actually powers off. (In this situation it is at least harmless to press and hold in order to force power off.)
My favorite is the procedure with the old HPPA Risc machines. You were taught to ALWAYS wait until the (SHUT 6) message is displayed. Well sometimes it never got there. Years later an more experienced Hewlett Packard Service Engineer said it was safe to power down after a (SHUT 4). He explained it was simply waiting for pin signals parent/child processes it was never going to get. (The parent had gone missing.)
This was also before the days of gender politically correct technical terms. We still called them Father-Son processes back then.
With a complex instruction set machine like your PC, who knows what signal it is waiting for? (Like my old HP Engineer friend also used to say, you’re going to kill it anyway, don’t worry about it.)
This just happened to me today for the first time ever ( Librem 15, 2019). Logo hung on for about 2 min and then closed. I am going to start making sure all applications are closed down before the power off next time to see if it goes away.