System Hung when moving Windows around on the Screen

[Frank Krauss]

Sirs,
I was running on this system after having re-booted it only about an Hour ago.
I had four(4) windows open on the user.
Two were vi sessions.
One was running a Program
and the last one was playing a video using mplayer.
I was simply attempting to move these windows around for better placement on the Screen.
I had moved the two VI sessions up higher on the screen and when I attempted to move
the Window that was playing the Video it hung up the System.
I could move the Mouse around but it didn't accept any clicks from it or any responses
from pressing keys.
When I pressed CTRL + ALT + F1, I was able to get to the Screen that shows all of my
Users on it, but it wouldn't allow me to select any of them.
I used the SysrRq - Magic Key combination to get the following information
ALT + PrtScrn, ALT + CREISUB
The system re-booted and gave me the usual files in /var/crash
In this case, I used the "sudo ubuntu-bug xxxxxx.crash" command to create this record
as per my instructions in problem # 1877890.
Please see that problem for my reason to create this problem this way.
If there is any information I can supply to help you correct these Hangups,
I would be happy to oblige.
Yours truly,
Frank Krauss

ProblemType: KernelCrash
DistroRelease: Ubuntu 18.04
Package: linux-image-5.3.0-51-generic 5.3.0-51.44~18.04.2
ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
Uname: Linux 5.3.0-51-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
Date: Mon May 18 16:58:48 2020
InstallationDate: Installed on 2020-04-20 (29 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

[Frank Krauss (fmfkrauss)]

Dear Sirs,
Please feel free to close out this Bug.
The Solution was to run with the 4.15.0 Nucleus.
The problem was probably caused by the fact that my Computer System was 10+ years old
and so it couldn't support the new HWE code in the 5.x Series.
If you look at bug 1877890 you will see a fuller description of the problem.
Yours truly,
Frank Krauss