I no longer have this issue. I don't know whether it was updating mdadm
or another package, but I recently issued a shutdown command and walked
over to my box to hold the power button for a few seconds and finish
shutting it off, only to find it was already off. I've since confirmed
that a reboot c
Mine is an Intel NUC6i7KYK. As the model number suggests, it's an Intel
NUC with a Skull Canyon (6th generation) i7 processor. Intel ARK link:
http://ark.intel.com/products/89187/Intel-NUC-Kit-NUC6i7KYK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
I can't quite figure out why, but the answer seems to be "occasionally".
I was able to reboot a few times (2 out of maybe 30?) using the complete
list of reboot= options. However, I suspect making the reboot= changes
is a red herring -- I rebooted the machine more in the past few hours
than I have
Public bug reported:
I tried getting more information in the debug-shell but I was
unsuccessful in doing so. I was able to switch to the debug shell via
ctrl+alt+f9 but I couldn't actually type anything in. I could switch
back to the stuck shutdown screen via ctrl+alt+f1, and hitting NumLock
would
