Several hours ago I started the updating process in Discover. When done I shutdown with “install updates and shutdown” or something like that.
Then, when the laptop was restarting and installing updates, I closed the lid and left.
A few hours later, I came back and opened the laptop to see the “Installing Updates” screen at 94%. It has been stuck on 94% for more than an hour now, which is highly unusual (I think it was only 4 updates to install).
So how can I get the updates to finish now? Or is it safe to simply turn the laptop off while updates are being installed?
Using a Huawei Matebook 14s, probably pretty current KDE Neon (can’t check for obvious reasons)
Hi - if you still have that device sitting in that state, are you able to switch to a pure terminal interface using Ctrl+Alt+F2 or Ctrl+Alt+F3 and see what’s running?
In general, it might be a bit risky to close a laptop lid during an update process - how that minimal “install updates” session interacts with your hardware in handling the lid closing might not totally match how you have your personal desktop session configured.
Thanks for the reply. Unfortunately Ctrl+Alt+F2 (or others) do nothing, except sometimes flashing the screen.
In general, it might be a bit risky to close a laptop lid during an update process - how that minimal “install updates” session interacts with your hardware in handling the lid closing might not totally match how you have your personal desktop session configured.
I didn’t expect that the OS would react to closing the lid this early (before login screen). My expectation was that it would just do the updates and then shut down, whatever the lid state.
I don’t know that it necessarily would always cause a problem to close the lid, I’ve just been burned in the past by laptops (both Windows and Linux) doing things I really wished they didn’t when I closed the lid around shutdown or startup time!
If it’s already enabled, it might be time to try Magic SysRq? (Alt+PrtSc and keep holding down Alt while typing R, E, I, S, U, B - for reference: Magic SysRq key - Wikipedia )
If it’s already enabled, it might be time to try Magic SysRq?
This worked. The cogwheel stopped spinning and some 10 sec later the system rebooted.
I can’t tell whether the updates were applied correctly, but at least the system is usable now, nothing obviously broken, and installing other updates works.