[Solved] - Tower's 1st [no, 3rd] Hard-Reset since clean-reinstall.

[kdemeoz]

You could try one of these possible solutions.
http://askubuntu.com/questions/483416/ke...er-suspend
https://ubuntuforums.org/showthread.php?...007&page=2
And this an old post but looks promising.
https://forums.linuxmint.com/viewtopic.php?t=152185

I have now read those pages per your links - thanks. The key theme therein seems to be to edit grub from its Maui-standard:

Code:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

...to become:

Code:

GRUB_CMDLINE_LINUX_DEFAULT="atkdb.reset i8042.nomux quiet splash"

The https://askubuntu.com/questions/483416/k...er-suspend link says "This also works on 16.04".

My associated question is this; the context for that putative solution on those pages is "Every time it resumes from being suspended, neither the keyboard nor mouse work". However that is not a fair description of my scenario. I Suspend both my Tower & my Lappy [each runs Maui] every night, before going to bed, then Resume them the following day to continue my activities. As best i can recollect, Lappy's Maui has never misbehaved with the dead lockscreen at Resume, & though Tower has done so, it is once-only since my 31/12/16 rebuild, & maybe twice maximum since my Sept 2016 original installation, until 31/12. 

That being so, do you Pliny, or you leszek, or anyone else who cares to comment, really feel my rare instances of this fault justify making that grub edit? I am not resistant to it, only i want to know that any change i make is actually valid AND necessary [oh, & not with bad side-effects either, of course].